Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: "H . J . Lu" <hjl@lucon.org>, GDB <gdb@sources.redhat.com>
Subject: Re: gdb doesn't work well with DSO on Linux/mips
Date: Mon, 25 Mar 2002 20:32:00 -0000	[thread overview]
Message-ID: <20020325233301.A3581@nevyn.them.org> (raw)
In-Reply-To: <1020326040549.ZM14741@localhost.localdomain>

On Mon, Mar 25, 2002 at 09:05:49PM -0700, Kevin Buettner wrote:
> On Mar 23, 11:52am, Daniel Jacobowitz wrote:
> 
> > > 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.
> 
> Yes, I prefer this as well.
> 
> > 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?
> 
> Wouldn't this cause problems when debugging ordinary statically linked
> programs?  After all, we'd be putting solib event creation breakpoints
> on symbols like main and _start.

We'll already do this, I think.

> Or were you referring to symbols like r_debug_state, etc?  If that's
> the case, I think it'd be okay.

Yes, that's what I meant.  I was thinking of _dl_debug_state, which I
believe is the glibc equivalent of r_debug_state.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2002-03-26  4:32 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
2002-03-25 20:06     ` Kevin Buettner
2002-03-25 20:32       ` Daniel Jacobowitz [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=20020325233301.A3581@nevyn.them.org \
    --to=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