From: "Christophe Benoit" <cbenoit@aastra.com>
To: <gdb@sourceware.org>
Subject: Cannot get thread event message: debugger service failed
Date: Thu, 26 Oct 2006 12:41:00 -0000 [thread overview]
Message-ID: <516F0B1903234D4FBF41BAF138F56E4459FD11@Guymail1.fr.aastra.com> (raw)
In-Reply-To: <453F0CA7.7070309@netspace.net.au>
[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]
Hi everybody,
I am trying to use gdb script on a multithreaded application.
My script is very simple :
- Attach on the process
- I set a breakpoint
- I use a while statement to reach the breakpoint fifty times
- After that, I delete the breakpoint, detach and quit.
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
The command is : gdb -batch -x scriptgdb.withoutserv.out
I don't know what the problem is, may be on the way I use gdb ? (The
script is in attachment)
It seems that gdb have some problems with the multithreaded application,
is it a known "bug" ?
Any help will be appreciated.
Regards,
Christophe
--
Christophe BENOIT, Production logiciels 6500
AASTRA MATRA Telecom
1 rue Arnold Schoenberg
78280 Guyancourt
e-mail: christophe.benoit@aastra.com
[-- Attachment #2: scriptgdb.withoutserv.out --]
[-- Type: application/octet-stream, Size: 1117 bytes --]
echo -- Suppression de la pagination\n
set pagination off
echo -- Mise en route verbose et complaint
set verbose on
set complaints 5
show complaints
set confirm off
echo -- Valeur de scheduler-locking\n
show scheduler-locking
echo \n-- Attache sur PID\n
attach 15809
echo \n-- On coupe le Watchdog\n
print maid_system[3]
set maid_system[3]=0
print maid_system[3]
echo \n-- Pose du breakpoint\n
break cm291aaa.c:1362
c
echo \n-- Info threads\n
info threads
set $IND=0
# On ne passe que 5 fois dans le breakpoint
while($IND != 50)
printf "\n-- Breakpoint rencontre pour la %d fois\n",$IND
#echo \n-- Listing du code du breakpoint :\n
#list
echo \n-- Valeurs des variables locales\n
info local
# echo \n-- Info threads\n
# info threads
echo \n-- Info process\n
info proc
# On continue lexecution
echo \n-- Continue\n
c
echo \n-- Breakpoint atteint\n
set $IND += 1
end
echo \n-- Suppression du breakpoint\n
delete breakpoints
echo \n-- On remet le Watchdog\n
print maid_system[3]
set maid_system[3]=65535
print maid_system[3]
echo \n-- On se detache du process\n
detach
quit
next prev parent reply other threads:[~2006-10-26 12:41 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 ` Christophe Benoit [this message]
2006-10-26 12:45 ` Cannot get thread event message: debugger service failed Daniel Jacobowitz
2006-10-26 13:31 ` Christophe Benoit
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=516F0B1903234D4FBF41BAF138F56E4459FD11@Guymail1.fr.aastra.com \
--to=cbenoit@aastra.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