Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <Michael.Snyder@palmsource.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: Error running remote gdb
Date: Sat, 02 Sep 2006 00:05:00 -0000	[thread overview]
Message-ID: <1157155509.4466.96.camel@localhost.localdomain> (raw)
In-Reply-To: <20060901040853.GB27656@nevyn.them.org>

On Fri, 2006-09-01 at 00:08 -0400, Daniel Jacobowitz wrote:
> On Thu, Aug 31, 2006 at 08:31:34PM -0700, Michael Snyder wrote:
> > The last message from gdb to the target, "$vCont;s:6098;c#67",
> > doesn't seem to make sense.
> 
> Does to me.  Probably breakpoint_here_p has failed, for some reason.

I meant, "doesn't make sense unless something else is wrong".
Ie., if for instance breakpoint_here_p has NOT failed, then
gdb should have stepped over the breakpoint before continuing.

I wonder why breakpoint_here_p would fail?  It's a fairly
simple function, there's only one breakpoint, and it doesn't
fail very commonly (to my knowledge).

> I've seen this related to DECR_PC_AFTER_BREAK breakage, but on PPC
> that's unlikely unless the GDB in question is very badly misconfigured.

Right -- well, if that's the case, then it will still fail
if Bizhan runs the experiment that I suggested, with vCont
out of the picture.  We should see gdb issue an ordinary
continue request, without first stepping over the breakpoint.


  reply	other threads:[~2006-09-02  0:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-01  0:33 Bizhan Gholikhamseh (bgholikh)
2006-09-01  0:35 ` Daniel Jacobowitz
2006-09-01  3:31 ` Michael Snyder
2006-09-01  4:09   ` Daniel Jacobowitz
2006-09-02  0:05     ` Michael Snyder [this message]
2006-09-02  1:04       ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2006-09-08  2:01 Bizhan Gholikhamseh (bgholikh)
2006-09-08  1:30 FW: " Bizhan Gholikhamseh (bgholikh)
2006-09-08  1:53 ` Michael Snyder
     [not found] <F795765B112E7344AF36AA911279641502D19B97@xmb-sjc-212.amer.cisco.com>
2006-09-08  1:27 ` Michael Snyder
2006-09-08  2:12   ` Daniel Jacobowitz
2006-09-06 11:47 Bizhan Gholikhamseh (bgholikh)
2006-09-07 22:48 ` Michael Snyder
2006-08-31  0:39 Bizhan Gholikhamseh (bgholikh)
2006-08-31 22:47 ` Michael Snyder
2006-08-31 23:28   ` Daniel Jacobowitz
2006-09-01  3:13     ` Michael Snyder
2006-09-01  4:08       ` Daniel Jacobowitz
2006-08-30 22:37 Bizhan Gholikhamseh (bgholikh)
2006-08-30 23:11 ` Michael Snyder
2006-08-30 21:54 Bizhan Gholikhamseh (bgholikh)
2006-08-30 21:56 ` Daniel Jacobowitz
2006-08-30 23:08 ` Michael Snyder

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=1157155509.4466.96.camel@localhost.localdomain \
    --to=michael.snyder@palmsource.com \
    --cc=drow@false.org \
    --cc=gdb@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