From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21446 invoked by alias); 11 May 2008 00:38:02 -0000 Received: (qmail 21429 invoked by uid 71); 11 May 2008 00:38:02 -0000 Date: Sun, 11 May 2008 00:38:00 -0000 Message-ID: <20080511003802.21428.qmail@sourceware.org> To: nobody@sources.redhat.com Cc: gdb-prs@sources.redhat.com, From: Nick Roberts Subject: Re: gdb/2456: invalid gsdb reply Reply-To: Nick Roberts Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org X-SW-Source: 2008-q2/txt/msg00039.txt.bz2 The following reply was made to PR gdb/2456; it has been noted by GNATS. From: Nick Roberts To: ron.eggler@gmail.com Cc: gdb-gnats@sources.redhat.com Subject: Re: gdb/2456: invalid gsdb reply Date: Sun, 11 May 2008 12:29:02 +1200 > Linux (Kubuntu 8.04) KDevelop > >Description: > I wanted to debug an application written on a different system and got some > ABORT message - okay, I restarted it and stepped thru it, then once a couple > of threads get started i get a message from gdb saying: "Invalid gdb reply > > The 'stopped' packet does not include the 'reason' > field'. > > Details > The gdb reply is: bla-bla-bla" > > This made me smiling but doesn't get me any further. This message should > probably be changed from bla-bla-bla to something that makes more sense ;) > > Thanks, > Ron > >How-To-Repeat: > just do it again Do what again? If this happens in KDevelop, you should report the problem there. Alternatively, it might work if you get current GDB from sourceware.org as GDB used to not include the reason for temporary breakpoints. This is just a guess though, as you haven't explained how you got the message. As an aside, it's proably best to make an initial report to gdb@sourcware.org where there is a wider audience. > >Fix: > replace the bla-bla-bla string :) > >Release-Note: > >Audit-Trail: > >Unformatted: -- Nick http://www.inet.net.nz/~nickrob