Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Doug Evans <dje@google.com>
Cc: gdb@sourceware.org, Pedro Alves <pedro@codesourcery.com>,
		Pierre Muller <muller@ics.u-strasbg.fr>
Subject: Re: New breakpoint_re_set call vs remote targets
Date: Thu, 25 Jun 2009 18:33:00 -0000	[thread overview]
Message-ID: <20090625183333.GA19506@caradoc.them.org> (raw)
In-Reply-To: <e394668d0906250952w276b5577j1059cfc47edfbb8a@mail.gmail.com>

On Thu, Jun 25, 2009 at 09:52:36AM -0700, Doug Evans wrote:
> I wonder if one useful step is to reassess post_create_inferior, and
> maybe split it up or something.

Adding it was a huge boon for consolidation.  I don't really want to
split it up again if we don't have to.  Lots of actions used to be
missed when using a particular target, such as remote or remote-mips
or even core.

Converting watchpoints from hardware to software (the point of the new
call) is a sensible thing to do at the point of connection.  It's just
the prologue skipping that's bitten us - I like Pedro's idea of doing
this at load.

> From my perhaps ancient point of view, gdb is for debugging two kinds
> of programs: hosted and freestanding (to borrow jargon from C - though
> non-bare-metal and bare-metal may be more accurate. 1/2 :-)), and I
> wonder if they're being inadvertently fused.

I've been wondering about this too... I fear that if we introduce any
switch between these two modes, we'll find it's not granular enough.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2009-06-25 18:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24 19:04 Daniel Jacobowitz
2009-06-24 23:36 ` Pedro Alves
2009-06-24 23:46   ` Daniel Jacobowitz
2009-06-24 23:53     ` Pedro Alves
2009-06-25 16:52 ` Doug Evans
2009-06-25 18:33   ` Daniel Jacobowitz [this message]
2009-06-25 19:36     ` Doug Evans

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=20090625183333.GA19506@caradoc.them.org \
    --to=drow@false.org \
    --cc=dje@google.com \
    --cc=gdb@sourceware.org \
    --cc=muller@ics.u-strasbg.fr \
    --cc=pedro@codesourcery.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