From: Michael Snyder <msnyder@specifix.com>
To: Paul Koning <Paul_Koning@dell.com>
Cc: gdb@sourceware.org
Subject: Re: Symbol tables for separately linked pieces
Date: Sat, 12 Jul 2008 02:35:00 -0000 [thread overview]
Message-ID: <1215830134.3549.237.camel@localhost.localdomain> (raw)
In-Reply-To: <18550.7195.371436.629820@gargle.gargle.HOWL>
On Thu, 2008-07-10 at 10:26 -0400, Paul Koning wrote:
> I have an application that consists of two parts, a main program which
> is one ELF image and a subsystem which is separately linked as an ELF
> image of its own. The latter is loade into a portion of the address
> space of the former at startup. The symbol table of the subsystem
> image reflects its final load address.
As others have said, this sort of anticipates the challenges
we will face with heterogenous multi-process debugging.
My separate question is, why wouldn't your application be
suitable for a shared library?
prev parent reply other threads:[~2008-07-12 2:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 14:27 Paul Koning
2008-07-10 14:58 ` Andrew STUBBS
2008-07-10 15:07 ` Daniel Jacobowitz
2008-07-10 15:56 ` Paul Koning
2008-07-10 16:13 ` Daniel Jacobowitz
2008-07-10 17:10 ` Stan Shebs
2008-07-14 19:04 ` Tom Tromey
2008-07-12 2:35 ` Michael Snyder [this message]
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=1215830134.3549.237.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=Paul_Koning@dell.com \
--cc=gdb@sourceware.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