From: Robin Getz <rgetz@blackfin.uclinux.org>
To: "Daniel Jacobowitz" <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: debugging something with multiple text sections inonecompilation unit
Date: Fri, 03 Aug 2007 23:04:00 -0000 [thread overview]
Message-ID: <200708031908.04984.rgetz@blackfin.uclinux.org> (raw)
In-Reply-To: <20070803140225.GA23632@caradoc.them.org>
On Fri 3 Aug 2007 10:02, Daniel Jacobowitz pondered:
> Take a look at how qOffsets works.
Will do - thanks
> qOffsets is not rich enough to specify what you need; but assuming you use
> sensible ELF segments, the new code in HEAD after 6.6 could be easily
> exteneded to take more than just a text and data segment. We just didn't,
> because we didn't have any users for that.
We do now. :)
We will have a look, and send a patch if we can get the copyright assignment
sorted with the FSF.
-Robin
prev parent reply other threads:[~2007-08-03 23:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 4:06 debugging something with multiple text sections in one compilation unit Robin Getz
2007-08-03 11:37 ` Daniel Jacobowitz
2007-08-03 13:57 ` debugging something with multiple text sections in onecompilation unit Robin Getz
2007-08-03 14:02 ` Daniel Jacobowitz
2007-08-03 23:04 ` Robin Getz [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=200708031908.04984.rgetz@blackfin.uclinux.org \
--to=rgetz@blackfin.uclinux.org \
--cc=drow@false.org \
--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