Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@gnat.com>
To: gdb-patches@sources.redhat.com, kettenis@gnu.org
Subject: Re: problem unwinding past pthread_cond_wait() on x86 RedHat 9.0
Date: Tue, 14 Oct 2003 16:21:00 -0000	[thread overview]
Message-ID: <20031014162155.GE989@gnat.com> (raw)
In-Reply-To: <20031014160220.GA11076@nevyn.them.org>

> >    % objdump --headers /lib/tls/libpthread.so.0 | grep frame
> >     15 .eh_frame_hdr 0000002c  00009dc8  00009dc8  00009dc8  2**2
> >     16 .eh_frame     0000010c  00009df4  00009df4  00009df4  2**2
> > 
> > No .debug_frame section (not a single dwarf2-related section for
> > that matter).
> 
> That is CFI.  The .eh_frame section is actually just about the same as
> the .debug_frame section, but encoded a little differently and loaded
> into memory instead of marked as a debugging section.

Ah, OK, thanks. Given the name of the section, I thought it would
contain exception handling _regions_, without necessarily providing
frame information for each and every function. I need to learn a bit
more about them...

-- 
Joel


  reply	other threads:[~2003-10-14 16:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-14  5:42 Joel Brobecker
2003-10-14 12:57 ` Daniel Jacobowitz
2003-10-14 15:24   ` Andrew Cagney
2003-10-14 15:46     ` Joel Brobecker
2003-10-14 15:52       ` Daniel Jacobowitz
2003-10-14 16:15         ` Andrew Cagney
2003-10-14 16:18           ` Daniel Jacobowitz
2003-10-14 16:19           ` Joel Brobecker
2003-10-14 15:53       ` Elena Zannoni
2003-10-14 15:58   ` Joel Brobecker
2003-10-14 16:02     ` Daniel Jacobowitz
2003-10-14 16:21       ` Joel Brobecker [this message]
2003-10-16 22:13         ` Richard Henderson
2003-10-15 19:34       ` Mark Kettenis
2003-10-23  1:07 ` Joel Brobecker
2003-10-23  2:41   ` 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=20031014162155.GE989@gnat.com \
    --to=brobecker@gnat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@gnu.org \
    /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