This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
Re: gdb/2456: invalid gsdb reply
- From: Nick Roberts <nickrob at snap dot net dot nz>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 11 May 2008 00:38:02 -0000
- Subject: Re: gdb/2456: invalid gsdb reply
- Reply-to: Nick Roberts <nickrob at snap dot net dot nz>
The following reply was made to PR gdb/2456; it has been noted by GNATS.
From: Nick Roberts <nickrob@snap.net.nz>
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