From: logitech <supriya.rao17@gmail.com>
To: gdb@sourceware.org
Subject: Sending signal to inferior program.
Date: Mon, 06 Jun 2011 17:32:00 -0000 [thread overview]
Message-ID: <31785488.post@talk.nabble.com> (raw)
Hi, I am currently working with the gdb source code. I wish to send a signal
to the inferior program at a specific time. I tried forking a thread in
gdb.c which sends signal to the inferior process. To get its pid, I declared
an extern variable shared between gdb.c and linux-nat.c
But this gives a seg fault. Also the signal doesn't seem to get delivered.
In linux-nat.c
if (debug_linux_nat)
fprintf_unfiltered (gdb_stdlog, "linux_nat_wait: [%s]\n",
target_pid_to_str (ptid));
gpid=ptid.pid; // gpid gets the pid value, the signal is sent to gpid
from gdb.c
Moreover when i debug this with flag set, gpid initially gets the value of
pid of inferior, but later it becomes -1.
Is there any other way in which I can accomplish this.
Thanks
--
View this message in context: http://old.nabble.com/Sending-signal-to-inferior-program.-tp31785488p31785488.html
Sent from the Sourceware - gdb list mailing list archive at Nabble.com.
next reply other threads:[~2011-06-06 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 17:32 logitech [this message]
2011-06-06 18:18 ` Jan Kratochvil
2011-06-06 20:25 ` logitech
2011-06-06 21:03 ` Jan Kratochvil
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=31785488.post@talk.nabble.com \
--to=supriya.rao17@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