From: Daniel Jacobowitz <dan@codesourcery.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [patch] Re: longjmp handling vs. glibc LD_POINTER_GUARD ?problems
Date: Thu, 22 May 2008 17:03:00 -0000 [thread overview]
Message-ID: <20080522031358.GA27933@caradoc.them.org> (raw)
In-Reply-To: <200805220014.m4M0EPrT004321@d12av02.megacenter.de.ibm.com>
On Thu, May 22, 2008 at 02:14:25AM +0200, Ulrich Weigand wrote:
> > But, x86 doesn't show any promise on that... The first time
> > we stop seeing the longjmp frame on the frame stack is much
> > earlier than the exit of longjmp:
> >
> > #0 0xf7e201d8 in ?? () from /lib32/libc.so.6
> > #1 0x00000001 in ?? ()
>
> So what's happening there? Is this some unrelated unwinder
> failure?
My guess: longjmp tail called to __siglongmp or some similarly named
not-exported function. So we can't find whatever frame setup there
was.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-05-22 3:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 18:24 longjmp handling vs. glibc LD_POINTER_GUARD problems Ulrich Weigand
2008-05-14 19:14 ` Daniel Jacobowitz
2008-05-14 22:01 ` Ulrich Weigand
2008-05-14 19:17 ` Pedro Alves
2008-05-17 14:00 ` Pedro Alves
2008-05-21 4:20 ` [patch] " Pedro Alves
2008-05-22 0:11 ` Ulrich Weigand
2008-05-22 0:14 ` Pedro Alves
2008-05-22 15:20 ` Pedro Alves
2008-05-22 15:34 ` Daniel Jacobowitz
2008-05-22 16:17 ` Pedro Alves
2008-05-22 16:38 ` Ulrich Weigand
2008-05-22 17:03 ` Daniel Jacobowitz [this message]
2008-05-22 16:29 ` Ulrich Weigand
2008-05-22 3:14 ` Daniel Jacobowitz
2008-05-14 23:03 ` David Miller
2008-05-15 0:39 ` Daniel Jacobowitz
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=20080522031358.GA27933@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=uweigand@de.ibm.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