Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Keith Seitz <keiths@redhat.com>, Tom Tromey <tromey@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: Some java questions
Date: Tue, 09 Sep 2008 21:31:00 -0000	[thread overview]
Message-ID: <20080909213028.GA16584@caradoc.them.org> (raw)
In-Reply-To: <m3bpyx9fy7.fsf@fleche.redhat.com> <48C6D1DF.3060705@redhat.com>

On Tue, Sep 09, 2008 at 12:43:27PM -0700, Keith Seitz wrote:
> In the case of jmisc,exp, the test suite attempts to set breakpoints on  
> "'jmisc.main(java.lang.String[])'" and  
> "'jmisc.main(java.lang.String[])void'", working around the gcc bug  
> (similar in jprint.exp). IMO, this is a very dangerous precedent. Bugs in 
> the toolchain should not be worked around like this. They should be  
> xfailed or (in this case), breaks at the correct "jmisc.main" should have 
> been left in as well.

See jmain.exp, which is specifically for this issue.

> At long last, my question is: Is gdb supposed to be able to do something  
> with "jmisc.main(java.lang.String[])void", i.e. is it considered valid  
> "input" to break, print, and other commands?

As long as it appears in the mangling - and gcj is going to continue
emitting DW_AT_MIPS_linkage_name, which I expect it will - I think it
ought to work.  Particularly with single quotes around it, as
jmisc.exp uses.

On Tue, Sep 09, 2008 at 03:17:52PM -0600, Tom Tromey wrote:
> FYI -- nobody really maintains the gcj support in gdb.

This is sad, but very much true.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-09-09 21:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-09 19:44 Keith Seitz
2008-09-09 21:18 ` Tom Tromey
2008-09-09 21:31   ` Daniel Jacobowitz [this message]
2008-09-09 23:39     ` Keith Seitz
2008-09-09 23:36   ` Keith Seitz

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=20080909213028.GA16584@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=keiths@redhat.com \
    --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