From: Eli Zaretskii <eliz@is.elta.co.il>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFA] procfs.c related changes for AIX 5
Date: Tue, 06 Mar 2001 01:41:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1010306113701.7922T-100000@is> (raw)
In-Reply-To: <1010306092900.ZM9261@ocotillo.lan>
On Tue, 6 Mar 2001, Kevin Buettner wrote:
> > > These syscall numbers are guaranteed (at least according to the
> > > developer that I spoke with) to be fixed for the lifetime of a
> > > process, but they can certainly vary between processes.
> >
> > Won't this cause problems with debugging syscall-related code, since
> > the values for GDB and the debuggee may be different?
>
> GDB knows the pid of the debuggee and interogates its syscall
> numbers in /proc/PID/sysent. I.e, it gets the syscall numbers
> for the child process that it's debugging from the /proc filesystem.
This probably takes care of most of the problems.
> If you're asking about actually debugging code that contains syscalls,
> I'm not sure I see how this enters the picture. Does GDB have some
> additional knowledge of syscall numbers somewhere that I'm not aware
> of?
It was just a thought; I didn't have any specifics in mind.
One possible complication is when GDB invokes a function from the
debuggee, and that function issues a system call. Again, just a
random thought.
> > Shouldn't these be documented somehow in gdbint.texinfo?
>
> Probably. (I'll take a look.)
Thanks!
next prev parent reply other threads:[~2001-03-06 1:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-05 18:58 Kevin Buettner
2001-03-06 1:11 ` Eli Zaretskii
2001-03-06 1:29 ` Kevin Buettner
2001-03-06 1:41 ` Eli Zaretskii [this message]
[not found] ` <3AAEC861.2756C62A@cygnus.com>
[not found] ` <msnyder@cygnus.com>
2001-03-26 18:24 ` Kevin Buettner
2001-07-30 5:47 Pb when calling a nested function in the inferior Joel Brobecker
2001-07-30 10:32 ` Michael Snyder
2001-07-30 11:31 ` Kevin Buettner
2001-07-30 14:24 ` Joel Brobecker
2001-07-30 15:41 ` Andrew Cagney
2001-07-30 15:49 ` Kevin Buettner
2001-07-31 0:24 ` Joel Brobecker
2001-07-31 1:20 ` Kevin Buettner
2001-07-31 1:36 ` Joel Brobecker
2001-07-31 1:29 ` Kevin Buettner
2001-08-23 3:40 ` Joel Brobecker
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=Pine.SUN.3.91.1010306113701.7922T-100000@is \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@cygnus.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