From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: forandom@gmail.com
Cc: gdb@sourceware.org
Subject: Re: Can the debugger get the sigaction table of the debugee?
Date: Thu, 25 Mar 2010 08:50:00 -0000 [thread overview]
Message-ID: <201003250850.o2P8omMF014478@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <77f815bd1003241923m5bd1f055la0999a7dec76dc1e@mail.gmail.com> (message from xingxing pan on Thu, 25 Mar 2010 10:23:39 +0800)
> Date: Thu, 25 Mar 2010 10:23:39 +0800
> From: xingxing pan <forandom@gmail.com>
>
> Can anyone help?
>
> 2010/3/24 xingxing pan <forandom@gmail.com>:
> > Can the debugger get the sigaction table of the debugee? when the user
> > wanna know the handler function of a specific signal.
> > It seems GDB can only get the siginfo struct through the syscall ptrace.
> >
> > Thank you.
None of the Unix-like kernels that that I'm familliar with expose this
information. Therefore, GDB cannot show it.
next prev parent reply other threads:[~2010-03-25 8:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 3:54 xingxing pan
2010-03-25 2:23 ` xingxing pan
2010-03-25 8:50 ` Mark Kettenis [this message]
2010-04-06 8:28 ` Hui Zhu
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=201003250850.o2P8omMF014478@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=forandom@gmail.com \
--cc=gdb@sourceware.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