From: Neo Jia <cjia@cse.unl.edu>
To: gdb@sources.redhat.com
Subject: GDB crashed when debugging execve() ... (thread_get_info_callback: cannot get thread info: generic error)
Date: Tue, 19 Jul 2005 23:36:00 -0000 [thread overview]
Message-ID: <1121815511.15516.141.camel@localhost.localdomain> (raw)
All,
I am using gdb to debug the JAVA VM. When the function execve() is
invoked, I got the following error messages.
thread_get_info_callback: cannot get thread info: generic error
The following is the procedure I got this error.
> gdb $JAVA_ROOT/java_g
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "x86_64-unknown-linux-gnu"...Using host
libthread_db library "/lib64/tls/libthread_db.so.1".
(gdb) b java_md.c:562
Breakpoint 1 at 0x4051ee: file ../../../../src/solaris/bin/java_md.c,
line 562.
(gdb) run -classpath . helloworld
Starting program: /home/cjia/j2sdk1.5.0-build/control/build/linux-
amd64/bin/java_g -classpath . helloworld
[Thread debugging using libthread_db enabled]
[New Thread 182894208224 (LWP 1893)]
[Switching to Thread 182894208224 (LWP 1893)]
Breakpoint 1, CreateExecutionEnvironment (_argcp=0x7fbffff4fc,
_argvp=0x7fbffff4f0,
jrepath=0x7fbfffe470 "/home/cjia/j2sdk1.5.0-
build/control/build/linux-amd64",
so_jrepath=4096,
jvmpath=0x5130f0 "/home/cjia/j2sdk1.5.0-build/control/build/linux-
amd64/lib/amd64/server", so_jvmpath=4096, original_argv=0x513010)
at ../../../../src/solaris/bin/java_md.c:562
562 execve(newexec, argv, newenvp);
(gdb) n
thread_get_info_callback: cannot get thread info: generic error
(gdb) n
Cannot find bounds of current function
(gdb) n
Cannot find bounds of current function
(gdb) where
#0 0x0000000000401850 in ?? ()
#1 0x0000000000405205 in CreateExecutionEnvironment (_argcp=Cannot
fetch general-purpose registers for thread 182894208224: generic error
)
at ../../../../src/solaris/bin/java_md.c:562
#2 0x0000000000000000 in ?? ()
#3 0x0000000000000000 in ?? ()
#4 0x0000000000000000 in ?? ()
#5 0x0000000000000000 in ?? ()
#6 0x0000000000000000 in ?? ()
#7 0x0000000000000000 in ?? ()
#8 0x0000000000000000 in ?? ()
#9 0x0000000000000000 in ?? ()
#10 0x0000000000000000 in ?? ()
#11 0x0000000000000000 in ?? ()
#12 0x0000000000000000 in ?? ()
#13 0x0000000000000000 in ?? ()
#14 0x0000000000000000 in ?? ()
#15 0x0000000000000000 in ?? ()
#16 0x0000000000000000 in ?? ()
#17 0x0000000000000000 in ?? ()
#18 0x0000000000000000 in ?? ()
#19 0x0000000000000000 in ?? ()
#20 0x0000000000000000 in ?? ()
#21 0x0000000000000000 in ?? ()
#22 0x0000000000000000 in ?? ()
#23 0x0000000000000000 in ?? ()
#24 0x0000000000000000 in ?? ()
#25 0x0000000000000000 in ?? ()
#26 0x0000000000000000 in ?? ()
---Type <return> to continue, or q <return> to quit---
#27 0x0000000000000000 in ?? ()
#28 0x0000000000000000 in ?? ()
#29 0x0000000000000000 in ?? ()
#30 0x0000000000000000 in ?? ()
#31 0x0000000000000000 in ?? ()
#32 0x0000000000000000 in ?? ()
#33 0x0000000000000000 in ?? ()
#34 0x0000000000000000 in ?? ()
#35 0x0000000000000000 in ?? ()
#36 0x0000000000000000 in ?? ()
#37 0x0000000000000000 in ?? ()
#38 0x0000000000000000 in ?? ()
#39 0x0000000000000000 in ?? ()
#40 0x0000000000000000 in ?? ()
#41 0x0000000000000000 in ?? ()
#42 0x0000000000000000 in ?? ()
#43 0x0000000000000000 in ?? ()
#44 0x0000000000000000 in ?? ()
#45 0x0000000000000000 in ?? ()
#46 0x0000000000000000 in ?? ()
#47 0x0000000000000000 in ?? ()
#48 0x0000000000000000 in ?? ()
#49 0x0000000000000000 in ?? ()
#50 0x0000000000000000 in ?? ()
#51 0x0000000000000000 in ?? ()
#52 0x0000000000000000 in ?? ()
#53 0x0000000000000000 in ?? ()
#54 0x0000000000000000 in ?? ()
---Type <return> to continue, or q <return> to quit---
#55 0x0000000000000000 in ?? ()
#56 0x0000000000000000 in ?? ()
#57 0x0000000000000000 in ?? ()
#58 0x0000000000000000 in ?? ()
#59 0x0000000000000000 in ?? ()
#60 0x0000000000000000 in ?? ()
#61 0x0000000000000000 in ?? ()
#62 0x0000000000000000 in ?? ()
#63 0x0000000000000000 in ?? ()
#64 0x0000000000000000 in ?? ()
#65 0x0000000000000000 in ?? ()
#66 0x0000000000000000 in ?? ()
#67 0x0000000000000000 in ?? ()
#68 0x0000000000000000 in ?? ()
#69 0x0000000000000000 in ?? ()
#70 0x0000000000000000 in ?? ()
#71 0x0000000000000000 in ?? ()
#72 0x0000000000000000 in ?? ()
#73 0x0000000000000000 in ?? ()
#74 0x0000000000000000 in ?? ()
#75 0x0000000000000000 in ?? ()
#76 0x0000000000000000 in ?? ()
#77 0x0000000000000000 in ?? ()
#78 0x0000000000000000 in ?? ()
#79 0x0000000000000000 in ?? ()
#80 0x0000000000000000 in ?? ()
#81 0x0000000000000000 in ?? ()
#82 0x0000000000000000 in ?? ()
---Type <return> to continue, or q <return> to quit---qq
Quit
(gdb) exit
Undefined command: "exit". Try "help".
(gdb) quit
The program is running. Exit anyway? (y or n) y
Quitting: thread_db_get_info: cannot get thread info: generic error
Thanks,
Neo
-----------------------------------------------------------------------------------
I would remember that if researchers were not ambitions
probably today we haven't the technology we are using!
reply other threads:[~2005-07-19 23:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1121815511.15516.141.camel@localhost.localdomain \
--to=cjia@cse.unl.edu \
--cc=gdb@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).