From: Alexandre Oliva <aoliva@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sources.redhat.com, roland@redhat.com
Subject: Re: Support Dwarf3 DW_CFA_val_* expressions
Date: Mon, 13 Mar 2006 06:23:00 -0000 [thread overview]
Message-ID: <orfyln13oa.fsf@free.oliva.athome.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20060311190811.GA26990@nevyn.them.org> (Daniel Jacobowitz's message of "Sat, 11 Mar 2006 14:08:11 -0500")
On Mar 11, 2006, Daniel Jacobowitz <drow@false.org> wrote:
> On Tue, Mar 07, 2006 at 02:46:00PM -0300, Alexandre Oliva wrote:
>> Using the address of the first instruction in the region wouldn't work
>> either. The hand-generated unwind info arranges for _L_mutex_lock_31
>> on i386 to seem like it calls itself, for some reason I don't quite
>> understand. Jakub says the backtrace we get after my change is
>> correct, whereas *without* the patch we get this:
> Where does this hand generated unwind info come from?
Jakub's testcase submitted as part of the patch.
--
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
Secretary for FSF Latin America http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}
next prev parent reply other threads:[~2006-03-13 2:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 17:54 Alexandre Oliva
2006-03-04 12:01 ` Mark Kettenis
2006-03-04 14:43 ` Alexandre Oliva
2006-03-04 15:07 ` Daniel Jacobowitz
2006-03-07 14:25 ` Alexandre Oliva
2006-03-07 15:01 ` Mark Kettenis
2006-03-07 19:55 ` Alexandre Oliva
2006-03-12 18:15 ` Mark Kettenis
2006-05-28 22:22 ` Alexandre Oliva
2006-03-13 2:25 ` Daniel Jacobowitz
2006-03-13 6:23 ` Alexandre Oliva [this message]
2006-03-24 23:08 ` 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=orfyln13oa.fsf@free.oliva.athome.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
--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