From: <tronics93-gdb@yahoo.com>
To: gdb@sources.redhat.com
Subject: Re: gdb 6.3 misses breakpoint on Linux when inferior does clone()
Date: Tue, 31 May 2005 17:06:00 -0000 [thread overview]
Message-ID: <20050531170523.45257.qmail@web31913.mail.mud.yahoo.com> (raw)
>> The kernel does not provide any interface for GDB to know whether
or
>> not a clone syscall has used CLONE_VM.
>>
>> [Satish] Doesn't ptrace(PTRACE_GETREGS,...) provide that
information >>? Or is that arch. specific ?
>No, it does not.
The following code snippet gets the flags passed in to clone() (on
x86):
unsigned long regs[FRAME_SIZE];
if (ptrace(PTRACE_GETREGS, pid, 0, ®s) < 0)
perror("ptrace_getregs failed:");
printf("syscall=%d, arg1=%#x, arg2=%#x\n", regs[ORIG_EAX],
regs[EBX], regs[ECX]);
--tronics93.
next reply other threads:[~2005-05-31 17:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 17:06 tronics93-gdb [this message]
2005-06-01 13:23 ` Daniel Jacobowitz
2005-06-11 23:31 ` Mark Kettenis
2005-06-12 0:23 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2005-05-26 20:02 Satish Mohan
2005-05-26 20:03 ` Daniel Jacobowitz
2005-05-26 19:40 Satish Mohan
2005-05-26 19:43 ` Daniel Jacobowitz
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=20050531170523.45257.qmail@web31913.mail.mud.yahoo.com \
--to=tronics93-gdb@yahoo.com \
--cc=gdb@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).