From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eli Zaretskii To: Kevin Buettner 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 Message-id: References: <1010306092900.ZM9261@ocotillo.lan> X-SW-Source: 2001-03/msg00106.html 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!