Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Markus Deuling <deuling@de.ibm.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] new set/show multiple-choice-auto-select commands (take 	2)
Date: Thu, 17 Jan 2008 14:26:00 -0000	[thread overview]
Message-ID: <20080117142615.GA8662@caradoc.them.org> (raw)
In-Reply-To: <478F3E4B.6050005@de.ibm.com>

On Thu, Jan 17, 2008 at 12:38:51PM +0100, Markus Deuling wrote:
> I implemented this behavior originally for the Cell BE combined
> debugger. Cell BE has binaries consisting of PowerPC- and
> SPU-code. If there is a symbol foo in both the PowerPC- and the
> SPU-part then GDB would always resolve the foo symbol from PowerPC
> (main executable) file no matter if it stands in a "SPU thread" or
> not. GDB recognizes SPU binaries as shared libraries.

Why shouldn't GDB default to setting both breakpoints... like we do
for template functions now?  At least, I thought that was the point of
all Vlad's work on breakpoints in the past year.  If you want
something more specific you can adjust the multiple-location
breakpoint.

I am concerned that we now have too many different places where we
have multiple symbols and breakpoints and we're handling them all
differently.

-- 
Daniel Jacobowitz
CodeSourcery


  parent reply	other threads:[~2008-01-17 14:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16 13:56 Joel Brobecker
2008-01-17  6:37 ` Markus Deuling
2008-01-17 10:27   ` Joel Brobecker
2008-01-17 11:41     ` Markus Deuling
2008-01-17 12:31       ` Joel Brobecker
2008-01-17 14:26       ` Daniel Jacobowitz [this message]
2008-01-17 14:51         ` Joel Brobecker
2008-01-17 15:07           ` Daniel Jacobowitz
2008-01-23 15:33             ` Joel Brobecker

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=20080117142615.GA8662@caradoc.them.org \
    --to=drow@false.org \
    --cc=brobecker@adacore.com \
    --cc=deuling@de.ibm.com \
    --cc=gdb-patches@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