public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "U. George" <gatgul@gatworks.com>
To: gdb@sourceware.org
Subject: why is "gdb /home/gat/JAVA/JDK16/jdk1.6.0/bin/java" so broken?
Date: Sat, 18 Feb 2006 18:39:00 -0000	[thread overview]
Message-ID: <43F76720.3050903@gatworks.com> (raw)

After some 60min of running javasoft's java, the program finally dies of 
a segfault. I have been trying, and apparently for several years now, 
according to the gdb bug base, to get GDB to work with java & threads.
Version 6.4 does not work any better.
there is something wrong in libthread_db.so. I'm not yet willing to just 
replace the libs, as this may affect the 'heap' bug that shows itself 
randomly.

So whats goin on with gdb?


> [gat@MyLaptop ~]$ gdb /home/gat/JAVA/JDK16/jdk1.6.0/bin/java
> GNU gdb Red Hat Linux (6.3.0.0-1.84rh)
> 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 "i386-redhat-linux-gnu"...(no debugging symbols found)
> Using host libthread_db library "/lib/tls/i686/libthread_db.so.1".
> 
> (gdb) r
> Starting program: /home/gat/JAVA/JDK16/jdk1.6.0/bin/java
> Reading symbols from shared object read from target memory...(no debugging symbols found)...done.
> Loaded system supplied DSO at 0xd46000
> (no debugging symbols found)
> [Thread debugging using libthread_db enabled]
> [New Thread 2251072 (LWP 2428)]
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> Cannot find user-level thread for LWP 2428: generic error
> (gdb)

             reply	other threads:[~2006-02-18 18:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-18 18:39 U. George [this message]
2006-02-18 19:09 ` Daniel Jacobowitz
2006-02-18 19:37   ` U. George
2006-02-19 18:08     ` Daniel Jacobowitz
2006-02-19 18:13       ` U. George
2006-06-21  2:33 ` Neo

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=43F76720.3050903@gatworks.com \
    --to=gatgul@gatworks.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).