Bug 117972 - signal backtrace broken
signal backtrace broken
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: gdb (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jan Kratochvil
David Lawrence
: 85247 85309 117028 121656 (view as bug list)
Depends On: 126089 126095 133782 133794 133799 136891
Blocks: 125157 170417
  Show dependency treegraph
Reported: 2004-03-10 12:07 EST by Andrew Cagney
Modified: 2007-11-30 17:07 EST (History)
7 users (show)

See Also:
Fixed In Version: gdb-
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-01-18 11:13:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andrew Cagney 2004-03-10 12:07:33 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1)

Description of problem:

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.set a breakpoint in a signal handler
2.run to the signal handler
3.do a backtrace

Actual Results:  (gdb) break handler
Breakpoint 1 at 0x10000470: file /tmp/segv.c, line 9.
(gdb) run
Starting program: /tmp/segv.32 

Program received signal SIGSEGV, Segmentation fault.
0x00000000 in ?? ()
(gdb) signal SIGSEGV
Continuing with signal SIGSEGV.

Breakpoint 1, handler (sig=11, info=0xffffe390, context=0x100004f4)
    at /tmp/segv.c:9
warning: Source file is more recent than executable.

9         exit (0);
(gdb) bt
#0  handler (sig=11, info=0xffffe390, context=0x100004f4) at /tmp/segv.c:9
#1  <signal handler called>
Cannot access memory at address 0xffffe430

Additional info:

#include <stdio.h>
#include <signal.h>
#include <ucontext.h>

static void
handler (int sig, siginfo_t *info, ucontext_t *context)
  exit (0);
static void
handler (int sig, int code, struct sigcontext *scp)
  exit (0);

static void
segv (void (*f) (void))

main ()
  static struct sigaction action;
  action.sa_sigaction = handler;
  action.sa_flags |= SA_SIGINFO;
  action.sa_handler = handler;
  sigaction (SIGSEGV, &action, NULL);
  segv (NULL);
Comment 1 Andrew Cagney 2004-03-10 12:09:32 EST
*** Bug 85247 has been marked as a duplicate of this bug. ***
Comment 2 Andrew Cagney 2004-03-10 12:12:30 EST
*** Bug 85309 has been marked as a duplicate of this bug. ***
Comment 3 David Lawrence 2004-03-15 13:53:33 EST
Changing product and version.
Comment 5 Andrew Cagney 2004-03-22 11:18:05 EST
- None of them handle this alternative signal handler, overhauling
signal handler unwinders to fix.
Comment 6 Andrew Cagney 2004-03-22 11:25:50 EST
*** Bug 117028 has been marked as a duplicate of this bug. ***
Comment 7 Johan Walles 2004-03-22 11:35:27 EST
I see this is "Platform: All", but I thought this was fixed on IA64
with the libunwind based gdb?
Comment 8 Andrew Cagney 2004-05-10 20:40:46 EDT
Yes, libunwind fixes the ia64 specific backtrace.  Unfortunatly it
doesn't fix step/finish/return/next when presented with such a stack
:-(  Both architecture specific and generic fixes are needed.
Comment 9 Andrew Cagney 2004-05-10 20:53:12 EDT
*** Bug 121656 has been marked as a duplicate of this bug. ***
Comment 11 Mike Ranweiler 2004-06-07 13:57:29 EDT
hijack summary to mirror for 121656
Comment 20 Johan Walles 2004-08-25 10:41:13 EDT
Can somebody explain to me why most bugs related to this one are
secret?  I fail to see how being unable to walk the stack in gdb can
relate to anything security sensitive, especially bug 121656 that has
been closed as a duplicate of this one.

It's quite annoying that almost every time I get an e-mail about this
bug it says the equivalent of "Something changed but I won't tell you
what, nyah, nyah.".
Comment 22 IBM Bug Proxy 2004-09-02 15:54:42 EDT
----- Additional Comments From manoji@us.ibm.com(prefers email via manjo@austin.ibm.com)  2004-09-02 15:50 -------
*** Bug 8850 has been marked as a duplicate of this bug. *** 
Comment 27 Johan Walles 2005-02-14 04:24:18 EST
This bug is NEEDINFO, but I cannot find any request for more info.  Is
any information needed, and if so, what, or has the Status just not
been updated?
Comment 28 IBM Bug Proxy 2005-07-11 15:27:15 EDT

           What    |Removed                     |Added
   Target Milestone|RHEL3_U4                    |RHEL3_U6

------- Additional Comments From corryk@us.ibm.com(prefers email via kevcorry@us.ibm.com)  2005-07-11 15:22 EDT -------
RHEL3-U4 is already out, so moving the target-milestone to RHEL3-U6. 

Note You need to log in before you can comment on or make changes to this bug.