From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: "H . J . Lu" <hjl@lucon.org>, GDB <gdb@sources.redhat.com>,
Kevin Buettner <kevinb@redhat.com>
Subject: Re: gdb doesn't work well with DSO on Linux/mips
Date: Sat, 23 Mar 2002 11:39:00 -0000 [thread overview]
Message-ID: <3C9CD9E4.7080302@cygnus.com> (raw)
In-Reply-To: <20020323115239.A29855@nevyn.them.org>
> This seems to work for me.
>>
>>
>> H.J.
>> ---
>> 2002-03-22 H.J. Lu (hjl@gnu.org)
>>
>> * config/mips/tm-linux.h (SOLIB_BKPT_NAME): New.
>
>
> Actually, I'd prefer the former (add __start to bkpt_names, after
> _start). One less thing to worry about when multi-arching.
>
> Also, it may be that we should check for the dynamic linker breakpoint
> symbols in the currently loaded BFD, if there is no .interp section.
> That would explicitly improve debugging of the dynamic linker. Kevin,
> does that sound reasonable?
Well, adding the macro is wrong :-)
Andrew
next prev parent reply other threads:[~2002-03-23 19:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-22 23:47 H . J . Lu
2002-03-23 0:08 ` H . J . Lu
2002-03-23 8:52 ` Daniel Jacobowitz
2002-03-23 11:39 ` Andrew Cagney [this message]
2002-03-25 20:06 ` Kevin Buettner
2002-03-25 20:32 ` 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=3C9CD9E4.7080302@cygnus.com \
--to=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=hjl@lucon.org \
--cc=kevinb@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