This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: tdep/1683: Can't backtrace from syscalls
- From: Andreas Schwab <schwab at suse dot de>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 29 Jun 2004 18:48:01 -0000
- Subject: Re: tdep/1683: Can't backtrace from syscalls
- Reply-to: Andreas Schwab <schwab at suse dot de>
The following reply was made to PR tdep/1683; it has been noted by GNATS.
From: Andreas Schwab <schwab@suse.de>
To: davidm@hpl.hp.com
Cc: 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 20:47:04 +0200
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.
The new interface is already in place, see
ia64-tdep.c:ia64_sigtramp_frame_sniffer.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."