From: Daniel Jacobowitz <dan@debian.org>
To: Ranga Iyengar <ambuga@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: siginfo of traced child to parent process
Date: Thu, 10 Apr 2003 18:06:27 -0400 [thread overview]
Message-ID: <20030410220626.GA32489@nevyn.them.org> (raw)
In-Reply-To: <20030410214141.67857.qmail@web40601.mail.yahoo.com>
On Thu, Apr 10, 2003 at 02:41:41PM -0700, Ranga Iyengar wrote:
> I wanted to know if there is a way to get the
> siginfo_t of a child process from a parent process.
> The child process is traced by the parent process
> using ptrace system call and if the child is stopped
> because of SIGSEGV or SIGFPE, the address of the
> instruction that caused the exception is available to
> the child from the signal handler thro' the siginfo
> structure. Is there any way of getting this
> info(siginfo) to the parent. The parent attaches to
> the child in the same way 'gdb' attaches to the
> debugged programs.
>
> I'm using linux kernel 2.4.18
There is in 2.5 - it's called PTRACE_GETSIGINFO. There isn't in 2.4.18
though.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-04-10 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 21:41 siginfo of traced child to parent process Ranga Iyengar
2003-04-10 22:06 ` Daniel Jacobowitz [this message]
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=20030410220626.GA32489@nevyn.them.org \
--to=dan@debian.org \
--cc=ambuga@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;
as well as URLs for NNTP newsgroup(s).