Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com, Roland McGrath <roland@redhat.com>
Subject: Re: [obish?sym;rfa:doc] Wire up vsyscall
Date: Fri, 07 May 2004 01:25:00 -0000	[thread overview]
Message-ID: <20040507012549.GA30182@nevyn.them.org> (raw)
In-Reply-To: <409AA61F.8050807@gnu.org>

On Thu, May 06, 2004 at 04:54:55PM -0400, Andrew Cagney wrote:
> >At present I know of the following problems:
> 
> 4.  backtrace changes:
> 
> #0  handler (sig=26, info=0xfeed7c50, context=0xfeed7cd0) at 
> /home/cygnus/cagney
> /PENDING/2004-05-06-add-vsyscall/src/gdb/testsuite/gdb.base/siginfo.c:31
> #1  0x0093e440 in __kernel_sigreturn ()
> #2  0x0804848a in main () at 
> /home/cygnus/cagney/PENDING/2004-05-06-add-vsyscall
> /src/gdb/testsuite/gdb.base/siginfo.c:66
> 
> vs
> 
> #0  handler (sig=26, info=0xfee1ea80, context=0xfee1eb00) at 
> /home/cygnus/cagney
> /GDB/src/gdb/testsuite/gdb.base/siginfo.c:31
> #1  <signal handler called>
> #2  0x0804848a in main () at 
> /home/cygnus/cagney/GDB/src/gdb/testsuite/gdb.base/
> 
> but remember I intend changing the second to:
> 
> ...
> #1 0x1234 in <signal trampoline>
> ...

In the meantime, here's the patch from my Debian backport which should
fix this.  Pending a way to indicate 'abnormal frame' status in the
CFI, we don't want to use it; frame_unwind_address_in_block will hit.

-- 
Daniel Jacobowitz

2004-01-25  Daniel Jacobowitz  <drow@mvista.com>

	* i386-tdep.c (i386_gdbarch_init): Check for signal frame first.
	* i386-linux-tdep.c (i386_linux_pc_in_sigtramp): Handle
	__kernel_sigreturn.

Index: gdb-6.1/gdb/i386-linux-tdep.c
===================================================================
--- gdb-6.1.orig/gdb/i386-linux-tdep.c	2004-04-05 13:26:42.000000000 -0400
+++ gdb-6.1/gdb/i386-linux-tdep.c	2004-04-05 13:26:46.000000000 -0400
@@ -227,6 +227,10 @@ i386_linux_pc_in_sigtramp (CORE_ADDR pc,
      exported from the shared C library, so the trampoline may appear to
      be part of the preceding function.  This should always be sigaction,
      __sigaction, or __libc_sigaction (all aliases to the same function).  */
+
+  if (name && strcmp (name, "__kernel_sigreturn") == 0)
+    return 1;
+
   if (name == NULL || strstr (name, "sigaction") != NULL)
     return (i386_linux_sigtramp_start (pc) != 0
 	    || i386_linux_rt_sigtramp_start (pc) != 0);
Index: gdb-6.1/gdb/i386-tdep.c
===================================================================
--- gdb-6.1.orig/gdb/i386-tdep.c	2004-04-05 13:26:42.000000000 -0400
+++ gdb-6.1/gdb/i386-tdep.c	2004-04-05 13:26:46.000000000 -0400
@@ -2013,6 +2013,10 @@ i386_gdbarch_init (struct gdbarch_info i
   /* Helper for function argument information.  */
   set_gdbarch_fetch_pointer_argument (gdbarch, i386_fetch_pointer_argument);
 
+  /* The signal handler might have dwarf2 CFI, via the vsyscall DSO, so check
+     for this first.  */
+  frame_unwind_append_sniffer (gdbarch, i386_sigtramp_frame_sniffer);
+
   /* Hook in the DWARF CFI frame unwinder.  */
   frame_unwind_append_sniffer (gdbarch, dwarf2_frame_sniffer);
 
@@ -2021,7 +2025,6 @@ i386_gdbarch_init (struct gdbarch_info i
   /* Hook in ABI-specific overrides, if they have been registered.  */
   gdbarch_init_osabi (info, gdbarch);
 
-  frame_unwind_append_sniffer (gdbarch, i386_sigtramp_frame_sniffer);
   frame_unwind_append_sniffer (gdbarch, i386_frame_sniffer);
 
   /* If we have a register mapping, enable the generic core file


  reply	other threads:[~2004-05-07  1:25 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-07  1:19 Andrew Cagney
2004-05-07  0:48 ` Roland McGrath
2004-05-07  1:31   ` Daniel Jacobowitz
2004-05-10 21:39     ` Andrew Cagney
2004-05-07  1:19 ` Andrew Cagney
2004-05-07  1:25   ` Daniel Jacobowitz [this message]
2004-05-10 21:27     ` Andrew Cagney
2004-05-11  5:15       ` Mark Kettenis
2004-05-11 14:49         ` Andrew Cagney
2004-05-11 14:53         ` Daniel Jacobowitz
     [not found]           ` <40A0FFB1.8030407@gnu.org>
2004-05-11 17:26             ` Daniel Jacobowitz
2004-05-12  0:28               ` Andrew Cagney
2004-05-15 20:58                 ` Mark Kettenis
2004-05-17 17:14                   ` Revamp sniffer; Was: " Andrew Cagney
2004-05-25 22:55                     ` Andrew Cagney
2004-06-11 17:32                       ` Andrew Cagney
2004-06-15 20:17                         ` Andrew Cagney
2004-06-16 23:07                           ` Roland McGrath
2004-06-24 18:10                             ` Andrew Cagney
2004-06-24 20:59                               ` Roland McGrath
2004-06-24 21:20                                 ` Mark Kettenis
2004-05-17 20:10 ` Andrew Cagney
     [not found]   ` <20040517131914.332fa347@saguaro>
2004-05-18  5:59     ` Eli Zaretskii
2004-05-18 20:09       ` Andrew Cagney
2004-05-19  5:50         ` Eli Zaretskii
2004-05-19 14:47           ` Andrew Cagney
2004-05-19 21:10             ` Eli Zaretskii
2004-05-20  5:33               ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040507012549.GA30182@nevyn.them.org \
    --to=drow@false.org \
    --cc=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=roland@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox