From: Daniel Jacobowitz <drow@false.org>
To: Aleksandar Ristovski <aristovski@qnx.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: patch: solib_break from _r_debug.r_brk
Date: Mon, 10 Oct 2011 02:32:00 -0000 [thread overview]
Message-ID: <CAN9gPaEKhXdwB0m9S2XHb-AMnQLq3zD85hXdzW0Z733cJ_R6Sw@mail.gmail.com> (raw)
In-Reply-To: <4E8A1D11.3070006@qnx.com>
On Mon, Oct 3, 2011 at 4:37 PM, Aleksandar Ristovski <aristovski@qnx.com> wrote:
> Tom, thanks for looking into this, but I have meanwhile done further testing
> on gnu/linux and uncovered that it is not worth pursuing. While it works for
> us, it doesn't on gnu/linux and I am not sure it can be made generic enough
> to defend it: http://sourceware.org/ml/gdb-patches/2011-10/msg00043.html
FWIW (not much), I looked into this area a year ago also. I thought
I'd posted a patch to use r_debug, but maybe not... Solaris does
something clever in which unrelocated values are available at link
time, so the debugger can pick them up right away - as long as it can
tell if they've been relocated, I guess. Linux just fills in zero
when it has the right value.
--
Thanks,
Daniel
next prev parent reply other threads:[~2011-10-10 2:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 13:57 Aleksandar Ristovski
2011-09-29 14:04 ` Marek Polacek
2011-09-29 14:32 ` Aleksandar Ristovski
2011-09-29 15:15 ` Aleksandar Ristovski
2011-10-03 19:51 ` Aleksandar Ristovski
2011-10-03 20:12 ` Tom Tromey
2011-10-03 20:40 ` Aleksandar Ristovski
2011-10-04 16:58 ` Tom Tromey
2011-10-04 17:59 ` Aleksandar Ristovski
2011-10-10 2:32 ` Daniel Jacobowitz [this message]
2011-10-12 21:16 ` Jan Kratochvil
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=CAN9gPaEKhXdwB0m9S2XHb-AMnQLq3zD85hXdzW0Z733cJ_R6Sw@mail.gmail.com \
--to=drow@false.org \
--cc=aristovski@qnx.com \
--cc=gdb-patches@sources.redhat.com \
--cc=tromey@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