Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <Michael.Snyder@palmsource.com>
To: "Bizhan Gholikhamseh (bgholikh)" <bgholikh@cisco.com>
Cc: gdb@sourceware.org
Subject: RE: Error running remote gdb
Date: Fri, 01 Sep 2006 03:31:00 -0000	[thread overview]
Message-ID: <1157081494.4466.71.camel@localhost.localdomain> (raw)
In-Reply-To: <F795765B112E7344AF36AA911279641502D19B54@xmb-sjc-212.amer.cisco.com>

On Thu, 2006-08-31 at 17:33 -0700, Bizhan Gholikhamseh (bgholikh) wrote:
>  

> > > Sending packet: $m3000ce98,4#c9...Ack Packet received: 9421fff0 
> > > Sending packet: $M3000ce98,4:7d821008#b1...Ack Packet received: OK 
> > > Sending packet: $m10000560,4#59...Ack Packet received: 48000181 
> > > Sending packet: $M10000560,4:7d821008#41...Ack Packet received: OK 
> > > Sending packet: $vCont;s:6098;c#67...Ack
> > 
> > Finally, gdb restores the breakpoints and tells the target to 
> > continue.
> > 
> > > Packet received: T0501:7ffffd30;40:10000560;thread:6098;
> > 
> > Whereupon we immediately hit the breakpoint at main.
> > This is where we went wrong.  This shouldn't have happened.
> 
> >Actually, this looks fine.  But we're at 0x10000560; why are we
> reinserting the breakpoint _at this address_ and >>then continuing?
> >Normally you leave the breakpoint out to step over it.
> 
> I> can't think what could cause that.
> 
> >> This is where I have to admit that I don't know the exact semantics
> of 
> >> the vCont message.  Over to you, Daniel?
> 
> >That's a "step only thread 6098, continue all other threads"
> >packet, in other words, it corresponds to a single step other than over
> a breakpoint.  If we're stepping over a >
> breakpoint we'd have not had the trailing ;c.
> 
> 
> Sorry I am a little confused here,

Understandable.  ;-)


>  so you are implying everything is
> fine, however I am not able to step or next?

Well, no, I think we're converging on 
"we don't exactly understand what's going on here".

The last message from gdb to the target, "$vCont;s:6098;c#67",
doesn't seem to make sense.  Personally I don't understand the 
semantics of vCont well enough to say for sure.

Fortunately, vCont can be turned off.   ;-)

Can you repeat the experiment approximately like this?
	% gdb test
	(gdb) set debug remote 1
	(gdb) set remote verbose-resume off
	(gdb) target remote 172.28.176.142:2001
	(gdb) break main
	(gdb) continue
	(gdb) where
	(gdb) step

Send us the result just like before.

Michael




  parent reply	other threads:[~2006-09-01  3:31 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 [this message]
2006-09-01  4:09   ` Daniel Jacobowitz
2006-09-02  0:05     ` Michael Snyder
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=1157081494.4466.71.camel@localhost.localdomain \
    --to=michael.snyder@palmsource.com \
    --cc=bgholikh@cisco.com \
    --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