tdep/1683: Can't backtrace from syscalls

David Mosberger davidm@napali.hpl.hp.com
Tue Jun 29 19:08:00 GMT 2004


The following reply was made to PR tdep/1683; it has been noted by GNATS.

From: David Mosberger <davidm@napali.hpl.hp.com>
To: Andreas Schwab <schwab@suse.de>
Cc: davidm@hpl.hp.com, gdb-gnats@sources.redhat.com,
	nobody@sources.redhat.com, gdb-prs@sources.redhat.com
Subject: Re: tdep/1683: Can't backtrace from syscalls
Date: Tue, 29 Jun 2004 11:59:22 -0700

 >>>>> On Tue, 29 Jun 2004 20:47:04 +0200, Andreas Schwab <schwab@suse.de> said:
 
   Andreas> David Mosberger <davidm@napali.hpl.hp.com> writes:
   >> Yes, of course, it's using the same code.  The problem is that
   >> IN_SIGTRAMP() has an ill-defined interface.  I assume/hope that
   >> whatever replacement is being worked on will be frame-based, in which
   >> case taking advantage of unw_is_signal_frame() will be trivial.
 
   Andreas> The new interface is already in place, see
   Andreas> ia64-tdep.c:ia64_sigtramp_frame_sniffer.
 
 OK, that's good.  Just to be clear, though: I'm not the gdb/ia64
 maintainer.  I worked on adding libunwind support to gdb to make sure
 the API is rich enough to support debuggers, but that was the extent
 of my involvement.
 
 	--david



More information about the Gdb-prs mailing list