Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [6.0] PROBLEMS and NEWS
Date: Mon, 22 Sep 2003 07:21:00 -0000	[thread overview]
Message-ID: <3F6EA2D4.7060906@redhat.com> (raw)
In-Reply-To: <3F6CBFA5.7060308@redhat.com>

> someone>   A long-standing bug involving Java and dynamic libraries has been
> someone>   fixed.  Support for Java debugging remains minimal, however.
> 
> ac> Do you have something more specific?  That could mean anything.
> 
> The "long-standing bug" was gdb/1322.
> 
>   http://sources.redhat.com/gdb/bugs/1322
>   "internal-error: sect_index_text not initialized" after printing a java type

Thanks, I'll add:

* Java

A long standing bug involving Java and dynamic libraries has been fixed 
(Ref: gdb/1322: "internal-error: sect_index_text not initialized" after 
printing a java type).

Hmm, did the equally long standing print java string bug also get fixed?

> I don't know what "minimal" means, specifically.

I'm told that It works really well at backtraces, but starts to struggle 
when printing variables, values, and objects, and really struggles with 
dynamic compiled/loaded shared libraries.  As for byte codes :-)

Andrew



  parent reply	other threads:[~2003-09-22  7:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-20 20:59 Andrew Cagney
2003-09-20 22:35 ` Daniel Jacobowitz
2003-09-20 23:39   ` Andrew Cagney
2003-09-22  7:21 ` Andrew Cagney [this message]
2003-09-22 19:12 ` Andrew Cagney
2003-09-22 22:16   ` Jim Blandy
2003-09-23 19:49     ` Andrew Cagney
2003-09-23 22:00       ` Jim Blandy
2003-09-25 18:30 ` Andrew Cagney
2003-09-22  7:38 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=3F6EA2D4.7060906@redhat.com \
    --to=ac131313@redhat.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