From: Daniel Jacobowitz <drow@mvista.com>
To: Gdb List <gdb@sources.redhat.com>
Subject: Re: question about method naming
Date: Mon, 06 May 2002 16:07:00 -0000 [thread overview]
Message-ID: <20020506230733.GA25065@nevyn.them.org> (raw)
In-Reply-To: <87adrc6frc.fsf@creche.redhat.com>
On Mon, May 06, 2002 at 05:03:19PM -0600, Tom Tromey wrote:
> >>>>> "Daniel" == Daniel Jacobowitz <drow@mvista.com> writes:
>
> Tom> If I type:
> Tom> b x.main
> Tom> gdb tells me that there is no such method.
>
> Daniel> Are you working on a very current gcj? I.E. one that defaults
> Daniel> to DWARF-2 output? I observe the same thing in 3.0.4 with
> Daniel> -gdwarf-2, but not with -gstabs+.
>
> Yes. I'm using the trunk cvs gcj.
>
> Daniel> In this version, the stabs debug info claims that 'class x'
> Daniel> has a member function 'main'. In DWARF-2 it claims that
> Daniel> 'class x' has a member function 'x.main(java.lang.String[])'.
> Daniel> If this is still the case in your compiler (check readelf -w
> Daniel> output, search for a DW_TAG_subprogram whose name contains
> Daniel> main) then I believe it is a gcj bug.
>
> Ok. What is the correct output? `main(java.lang.String[])'?
No, `main'. The type should not be there at all. Breaking on
`x.main(java.lang.String[])' or something similar should still work,
because the mangled name is in scope...
> I wonder if this was done because of the lack of namespace support in
> gdb? In this case that would be strange (`x' is a class, not a
> namespace). This is something I'll note in the bug report.
That may be why.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-05-06 23:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-06 10:44 Tom Tromey
2002-05-06 12:33 ` Daniel Jacobowitz
2002-05-06 15:53 ` Tom Tromey
2002-05-06 16:07 ` Daniel Jacobowitz [this message]
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=20020506230733.GA25065@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@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