Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit/java] Work around java/1565 in jmisc.exp
Date: Tue, 24 Feb 2004 16:46:00 -0000	[thread overview]
Message-ID: <20040224164625.GA25546@nevyn.them.org> (raw)
In-Reply-To: <403B7F03.4050009@gnu.org>

On Tue, Feb 24, 2004 at 11:42:43AM -0500, Andrew Cagney wrote:
> > we need to strip arguments and parentheses from DW_AT_name for 
> language_java and then I
> >expect it will start working.
> 
> FYI, a hack stripping that stuff didn't appear to make it work, and 
> doesn't fix the underlying problem of corrupt debug info.  As with Ada, 
> Java needs a better symbol search method.  What happened to that thread?

I imagine it got queued, just like everything else.

>   I want to finish my current massacre of
> >dwarf2read before I go playing with that, though - it's always been on
> >a lower burner.
> 
> Um, you appear to be spreading yourself very very thin here :-(

That's why I'm working from oldest to newest :)  Two of the oldest
messages in my gdb-patches TODO folder rely on the intercu work I've
done this week.  After that I think I may be stuck changing my TOOD
algorithm, or going back to working on multiple address breakpoints -
which means, going back to symbol searching.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2004-02-24 16:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-24 16:12 Andrew Cagney
2004-02-24 16:15 ` Daniel Jacobowitz
2004-02-24 16:42   ` Andrew Cagney
2004-02-24 16:46     ` Daniel Jacobowitz [this message]
2004-02-24 17:07 ` David Carlton
2004-02-24 17:47   ` Andrew Cagney
2004-02-24 17:49     ` Daniel Jacobowitz
2004-02-24 19:55       ` Andrew Cagney
2004-02-24 17:53     ` David Carlton
2004-02-24 16:33 Michael Elizabeth Chastain
2004-02-24 17:21 ` Andrew Cagney

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=20040224164625.GA25546@nevyn.them.org \
    --to=drow@false.org \
    --cc=cagney@gnu.org \
    --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