From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6179 invoked by alias); 1 Sep 2006 03:31:42 -0000 Received: (qmail 6168 invoked by uid 22791); 1 Sep 2006 03:31:41 -0000 X-Spam-Check-By: sourceware.org Received: from mx2.palmsource.com (HELO mx2.palmsource.com) (12.7.175.14) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 01 Sep 2006 03:31:39 +0000 Received: from localhost (localhost [127.0.0.1]) by localhost.domain.tld (Postfix) with ESMTP id CF50E26D6E; Thu, 31 Aug 2006 20:31:37 -0700 (PDT) Received: from mx2.palmsource.com ([127.0.0.1]) by localhost (mx2.palmsource.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 28431-06; Thu, 31 Aug 2006 20:31:36 -0700 (PDT) Received: from ussunex01.palmsource.com (unknown [192.168.101.9]) by mx2.palmsource.com (Postfix) with ESMTP id 0EAF226D65; Thu, 31 Aug 2006 20:31:36 -0700 (PDT) Received: from 192.168.92.59 ([192.168.92.59]) by ussunex01.palmsource.com ([192.168.101.9]) via Exchange Front-End Server owa.palmsource.com ([10.0.20.17]) with Microsoft Exchange Server HTTP-DAV ; Fri, 1 Sep 2006 03:31:35 +0000 Received: from svmsnyderlnx by owa.palmsource.com; 31 Aug 2006 20:31:34 -0700 Subject: RE: Error running remote gdb From: Michael Snyder To: "Bizhan Gholikhamseh (bgholikh)" Cc: gdb@sourceware.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Fri, 01 Sep 2006 03:31:00 -0000 Message-Id: <1157081494.4466.71.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-09/txt/msg00005.txt.bz2 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