Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: Fix Java PR gdb/1322 (was Re: [rfa/doc] Document pr gdb/1322 in PROBLEMS)
Date: Tue, 26 Aug 2003 03:09:00 -0000	[thread overview]
Message-ID: <20030826030915.GA6197@nevyn.them.org> (raw)
In-Reply-To: <8665kmg7vr.fsf@elgar.kettenis.dyndns.org>

On Sun, Aug 24, 2003 at 09:42:16PM +0200, Mark Kettenis wrote:
> Daniel Jacobowitz <drow@mvista.com> writes:
> 
> > On Mon, Aug 18, 2003 at 02:32:20PM -0400, Michael Elizabeth Chastain wrote:
> > > + 
> > > + gdb/1322: "internal-error: sect_index_text not initialized" after printing a java type
> > > + 
> > > + When gdb debugs a Java program which uses shared libraries, it can
> > > + generate this internal error.
> > > + 
> > > + If you get this error when debugging Java, you can try working around
> > > + the problem by relinking your program with no shared libraries at all
> > > + (even the standard C library).  With the GNU linker, use the "-static"
> > > + argument to do this.
> > > + 
> > > + You can also try this patch for gdb:
> > > + 
> > > +   http://sources.redhat.com/ml/gdb-prs/2003-q3/msg00190.html
> > 
> > How about we fix it instead?  This patch depends on Mark K's
> > per-objfile-data patch, but only because it touches the same area, I
> > think.
> > 
> > Dwarf maintainers, is this OK?  Could someone test that it fixes the
> > Java problems on HEAD?
> 
> I'm not exactly a DWARF maintainer, but since I wrote the code in that
> file I assume I can approve your patch :-).  I'll do so if you'll add a
> 
>    gdb_assert (objfile->section_offsets);
> 
> just before the
> 
>    offset = ANOFFSET (...
> 
> to check the assumption you're making that the section offsets will be
> available when we have DWARF2 CFI.
> 
> Oh, and change the PR first line of the ChangeLog into java/1322 such
> that GNATS will notice your patch.  I believe it will ignore it if you
> use gdb/1322.

Thanks.  I've checked this in on HEAD.  In a couple of days, if all
goes well, I'll move it to the branch.

I removed it from PROBLEMS too, since hopefully it's no longer a
problem.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-08-26  3:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-18 18:32 [rfa/doc] Document pr gdb/1322 in PROBLEMS Michael Elizabeth Chastain
2003-08-24 16:56 ` Fix Java PR gdb/1322 (was Re: [rfa/doc] Document pr gdb/1322 in PROBLEMS) Daniel Jacobowitz
2003-08-24 19:42   ` Mark Kettenis
2003-08-26  3:09     ` Daniel Jacobowitz [this message]
2003-08-25 15:56 ` [rfa/doc] Document pr gdb/1322 in PROBLEMS Andrew Cagney
2003-08-24 19:48 Fix Java PR gdb/1322 (was Re: [rfa/doc] Document pr gdb/1322 in PROBLEMS) Michael Elizabeth Chastain

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=20030826030915.GA6197@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@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