From: <gan_xiao_jun@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: about "SIGRT_0 (Unknown signal 32)"
Date: Sat, 30 Jul 2005 08:59:02 -0700 (PDT) [thread overview]
Message-ID: <20050730155902.54885.qmail@web53901.mail.yahoo.com> (raw)
Hi,
I am trace the reason of a segment fault.
I found it is created by a readdir loop by add fprintf
before&after it.
I use strace and get following information:
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
write(3,
"\3\0\0\0\0\0\0\0\275\4\0\0\0\0\0\0\f\0\0\0\0\0\0\0\275"...,
196) = 196
close(3) = 0
write(15,
"\300\\\27A\2\0\0\0\0\0\0\0Hx\2@\0\0\0@`\2\0@\0\320\1@\320"...,
148) = 148
rt_sigprocmask(SIG_SETMASK, NULL, [32], 8) = 0
rt_sigsuspend([] <unfinished ...)
--- SIGRT_0 (Unknown signal 32) ---
<... rt_sigsuspend resumed> ) = 32
sigreturn() = -1 EINTR
(Interrupted system call)
wait4(355, NULL, __WCLONE, NULL) = 355
munmap(0x40a2f000, 4096) = 0
_exit(0) = ?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I am not sure if the segment fault related with
Unknown signal 32. What is the meaning of it?
What does rt_sigsuspend do in these lines?
Thanks for any comment.
gan
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
reply other threads:[~2005-07-30 15:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050730155902.54885.qmail@web53901.mail.yahoo.com \
--to=gan_xiao_jun@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®