From: Roman Shaposhnick <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] impressive
Date: Tue, 25 Apr 2006 10:53:02 -0700 [thread overview]
Message-ID: <20060425175302.GH25096@submarine> (raw)
In-Reply-To: <20060425091701.Q21356@mrwint.cisco.com>
On Tue, Apr 25, 2006 at 09:17:01AM +0100, Derek Fawcus wrote:
> On Mon, Apr 24, 2006 at 08:51:17PM -0700, Roman Shaposhnick wrote:
> > On Tue, Apr 25, 2006 at 03:37:04AM +0100, Derek Fawcus wrote:
> > > > Well, this is to unwind trough exceptions through the C stack:
> > >
> > > There is no c++ code here, last I looked there is no c++ in dietlibc.
> >
> > That's the beauty of a shared library
>
> Well it must be junk in the linker script, I just can't be bothered to
> track it down and fix it. This section is not in the .o; and the output
> was a static file. So there is no call for the .eh_frame as this is not
> an AMD64 - it is a plain old 32 bit x86.
You can call it whatever you want. I explained the reasons it is there.
On top of which I can add that it *is* helpful to have .eh_frame if
any of your callers can be C++. Since I don't understand what part of the
explanation you don't understand the last thing I can add to this
conversation is that there are 2 kind of exception related sections
generate by two different components:
* .eh_frame is generate by the compiler (and these days even by the
C compiler running on arcs which don't strictly require it) and has
tables describing the stack layout and such. It is actually based
on DWARF2 and is rather difficult to get rid of, unless you want
to write linker scripts or use objcopy.
* .eh_frame_hdr is generated by the GNU ld when it sees --eh-frame-hdr
and has index for facilitating binary searches inside the actual
.eh_frame sections. This one you can skip by making sure GNU ld
is not given --eh-frame-hdr.
Thanks,
Roman.
next prev parent reply other threads:[~2006-04-25 17:53 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 20:37 Ronald G Minnich
2006-04-24 20:51 ` Charles Forsyth
2006-04-24 21:32 ` Brantley Coile
2006-04-25 11:06 ` Anthony Sorace
2006-04-25 11:08 ` Anthony Sorace
2006-04-25 2:15 ` Derek Fawcus
2006-04-25 2:23 ` Roman Shaposhnick
2006-04-25 2:37 ` Derek Fawcus
2006-04-25 3:51 ` Roman Shaposhnick
2006-04-25 8:17 ` Derek Fawcus
2006-04-25 17:53 ` Roman Shaposhnick [this message]
2006-04-26 1:11 ` Derek Fawcus
2006-04-26 1:19 ` Roman Shaposhnick
2006-04-26 2:12 ` Derek Fawcus
2006-04-25 3:02 ` Andy Newman
2006-04-25 3:13 ` Ronald G Minnich
2006-04-25 19:57 ` Dan Cross
2006-04-25 2:30 erik quanstrom
2006-04-25 2:48 ` Derek Fawcus
2006-04-25 10:20 erik quanstrom
2006-04-26 0:26 erik quanstrom
2006-04-26 0:48 ` geoff
2006-04-26 0:54 ` Roman Shaposhnick
2006-04-26 0:53 ` Roman Shaposhnick
2006-04-26 2:15 ` Taj Khattra
2006-04-26 4:59 ` David Leimbach
2006-04-26 12:37 ` Anthony Sorace
2006-04-26 15:28 ` Rian Hunter
2006-04-26 16:39 ` Micah Stetson
2006-04-26 18:02 ` Bruce Ellis
2006-04-26 20:14 ` Micah Stetson
2006-05-08 14:50 ` Harri Haataja
2006-05-08 15:04 ` LiteStar numnums
2006-05-08 15:12 ` Charles Forsyth
2006-05-08 20:08 ` Micah Stetson
2006-05-08 20:52 ` LiteStar numnums
2006-05-08 21:10 ` Jack Johnson
2006-05-08 21:17 ` andrey mirtchovski
2006-05-08 21:18 ` Paul Lalonde
2006-05-08 22:25 ` Francisco J Ballesteros
2006-05-09 21:56 ` Dave Eckhardt
2006-05-10 0:13 ` geoff
2006-05-10 8:39 ` Lluís Batlle
2006-05-08 23:31 ` geoff
2006-05-09 1:18 ` Paul Lalonde
2006-05-09 1:39 ` quanstro
2006-05-09 2:12 ` Paul Lalonde
2006-05-09 2:20 ` quanstro
2006-05-09 3:00 ` Paul Lalonde
2006-05-09 9:32 ` Bruce Ellis
2006-04-26 22:57 ` Roman Shaposhnick
2006-04-26 4:57 ` David Leimbach
2006-04-26 4:53 ` Ronald G Minnich
2006-04-26 5:11 ` Roman Shaposhnick
2006-04-26 0:55 erik quanstrom
2006-04-26 1:07 ` Roman Shaposhnick
2006-04-26 2:38 erik quanstrom
2006-04-26 3:24 jmk
2006-04-27 1:10 erik quanstrom
2006-04-27 2:06 ` Jack Johnson
2006-04-27 1:23 erik quanstrom
2006-04-27 5:08 ` Micah Stetson
2006-04-27 1:35 erik quanstrom
2006-04-27 2:13 erik quanstrom
2006-05-08 22:02 erik quanstrom
2006-05-10 0:45 erik quanstrom
2006-05-10 2:09 ` Lyndon Nerenberg
2006-05-10 3:35 ` David Arnold
2006-05-10 4:03 ` Lyndon Nerenberg
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=20060425175302.GH25096@submarine \
--to=rvs@sun.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).