This is the mail archive of the gdb-prs@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: tdep/1683: Can't backtrace from syscalls


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: gdb-gnats@sources.redhat.com, nobody@sources.redhat.com,
	davidm@hpl.hp.com, gdb-prs@sources.redhat.com
Subject: Re: tdep/1683: Can't backtrace from syscalls
Date: Mon, 28 Jun 2004 23:29:29 -0700

 >>>>> 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()).  But for now, I hope/assume your patch will be
 applied.
 
 Thanks,
 
 	--david


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]