From: Daniel Jacobowitz <drow@false.org>
To: "U. George" <gatgul@gatworks.com>
Cc: gdb@sourceware.org
Subject: Re: why is "gdb /home/gat/JAVA/JDK16/jdk1.6.0/bin/java" so broken?
Date: Sat, 18 Feb 2006 19:09:00 -0000 [thread overview]
Message-ID: <20060218183315.GA25033@nevyn.them.org> (raw)
In-Reply-To: <43F76720.3050903@gatworks.com>
On Sat, Feb 18, 2006 at 01:27:44PM -0500, U. George wrote:
> 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?
Probably the JDK does something funny with threads that bypasses
libthread_db.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-02-18 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-18 18:39 U. George
2006-02-18 19:09 ` Daniel Jacobowitz [this message]
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=20060218183315.GA25033@nevyn.them.org \
--to=drow@false.org \
--cc=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).