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 11:58: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 13:51:02 +0200
David Mosberger <davidm@napali.hpl.hp.com> writes:
>>>>>> On Sun, 27 Jun 2004 21:24:49 +0200, Andreas Schwab <schwab@suse.de> said:
>
> Andreas> http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=1683
> Andreas> Applying this patch fixes 22 failures in the testsuite.
>
> Andreas> -#define GATE_AREA_START 0xa000000000000100LL
> Andreas> +#define GATE_AREA_START 0xa000000000010700LL
>
> Rather fragile, but so was the old code and I see that IN_SIGTRAMP()
> has been deprecated, which is a good thing. Perhaps this code will
> vanish altogether in the future. On ia64, it'd be better to use
> libunwind to check whether a frame is a signal-trampoline frame (via
> unw_is_signal_frame()).
A gdb built with libunwind has exactly the same problem.
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."