From: "Christophe Benoit" <cbenoit@aastra.com>
To: "Daniel Jacobowitz" <drow@false.org>
Cc: <gdb@sourceware.org>
Subject: RE: Cannot get thread event message: debugger service failed
Date: Thu, 26 Oct 2006 13:31:00 -0000 [thread overview]
Message-ID: <516F0B1903234D4FBF41BAF138F56E4459FD12@Guymail1.fr.aastra.com> (raw)
In-Reply-To: <20061026124509.GA30286@nevyn.them.org>
> > The problem is that, sometimes, when the breakpoint is reach, gdb
goes
> > in error:
> >
> > [New Thread -1210061904 (LWP 15939)]
> > scriptgdb.withoutserv.out:56: Error in sourced command file:
> > Cannot get thread event message: debugger service failed
>
> Before today I'd never even seen that error, and now twice. I have no
> idea what is causing this. If you are using an older version of GDB,
> I recommend trying a current one; otherwise, we would need an
> application that can reproduce the problem.
Thanks Daniel,
I have just updated to the last release of gdb, the problem is always
here.
I will try to see with our development team if we can determine when
this problem occurred.
I will give you some feedback as soon as possible.
Christophe
>
> --
> Daniel Jacobowitz
> CodeSourcery
next prev parent reply other threads:[~2006-10-26 13:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 7:05 Gdb Russell Shaw
2006-10-25 12:49 ` Gdb Daniel Jacobowitz
2006-10-25 13:38 ` Gdb Russell Shaw
2006-10-25 14:17 ` Gdb Daniel Jacobowitz
2006-10-25 16:29 ` Gdb Russell Shaw
2006-10-25 20:16 ` Gdb Eli Zaretskii
2006-10-25 20:08 ` Gdb Eli Zaretskii
2006-10-26 2:28 ` Gdb Russell Shaw
2006-10-26 7:11 ` Gdb Eli Zaretskii
2006-10-26 8:16 ` Gdb Russell Shaw
2006-10-26 12:41 ` Cannot get thread event message: debugger service failed Christophe Benoit
2006-10-26 12:45 ` Daniel Jacobowitz
2006-10-26 13:31 ` Christophe Benoit [this message]
2006-10-26 20:01 ` Gdb Jim Blandy
2006-10-27 3:29 ` Gdb Russell Shaw
2008-11-25 8:10 Cannot get thread event message: debugger service failed D. Hugh Redelmeier
2008-12-01 22:27 ` 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=516F0B1903234D4FBF41BAF138F56E4459FD12@Guymail1.fr.aastra.com \
--to=cbenoit@aastra.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