From: Daniel Jacobowitz <drow@mvista.com>
To: David Carlton <carlton@kealia.com>
Cc: tromey@redhat.com, gdb <gdb@sources.redhat.com>,
Mark Kettenis <kettenis@gnu.org>
Subject: Re: GDB and Java
Date: Fri, 18 Jul 2003 16:46:00 -0000 [thread overview]
Message-ID: <20030718164612.GA19486@nevyn.them.org> (raw)
In-Reply-To: <yf2oezryed7.fsf@hawaii.kealia.com>
On Fri, Jul 18, 2003 at 09:43:48AM -0700, David Carlton wrote:
> On 18 Jul 2003 10:28:54 -0600, Tom Tromey <tromey@redhat.com> said:
>
> > Ok, I've tried cvs head today. I'm debugging a large java application
> > that consists of about 90 shared libraries (not including libgcj).
>
> > I can consistently make gdb crash like this:
>
> > ../../src/gdb/dwarf2-frame.c:1032: internal-error: sect_index_text not initialized
> > A problem internal to GDB has been detected,
> > further debugging may prove unreliable.
>
> This is probably the same unfortunate interaction between anonymous
> objfiles and the new DWARF 2 frame stuff that Daniel noted in
> conjunction with another patch of mine. I think
> <http://sources.redhat.com/ml/gdb-patches/2003-07/msg00264.html> is
> supposed to cure it, so give that a try. Is that patch, or a variant,
> supposed to go into 6.0? This argues that it had better go in.
I'm not sure if it's for the same issue or not, but that patch
definitely fixes Cygwin. Mark, everyone seems happy with that patch;
would you check it in on both branches?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-07-18 16:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 23:36 David Carlton
2003-06-12 3:47 ` Tom Tromey
2003-07-18 16:08 ` Tom Tromey
2003-07-18 16:12 ` Daniel Jacobowitz
2003-07-18 16:14 ` Tom Tromey
2003-07-18 16:36 ` Elena Zannoni
2003-07-18 16:38 ` Tom Tromey
2003-07-18 16:43 ` David Carlton
2003-07-18 16:46 ` Daniel Jacobowitz [this message]
2003-07-18 17:03 ` Andrew Cagney
2003-07-18 17:14 ` Tom Tromey
2003-07-18 18:38 ` Tom Tromey
2003-07-18 18:48 ` Kevin Buettner
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=20030718164612.GA19486@nevyn.them.org \
--to=drow@mvista.com \
--cc=carlton@kealia.com \
--cc=gdb@sources.redhat.com \
--cc=kettenis@gnu.org \
--cc=tromey@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