From mboxrd@z Thu Jan  1 00:00:00 1970
From: Daniel Berlin <dan@cgsoftware.com>
To: "Anthony Green" <green@redhat.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: gdb and gcj symbols
Date: Thu, 04 Oct 2001 23:28:00 -0000
Message-id: <11A6BFD1-B95A-11D5-8B45-0030657B5340@cgsoftware.com>
References: <005201c14d63$54b91000$5be6b4cd@cygnus.com>
X-SW-Source: 2001-10/msg00060.html

On Friday, October 5, 2001, at 02:02  AM, Anthony Green wrote:

> GDB's java support is quite broken right now.  Here's an example...
>
> (gdb) set lang java
> (gdb) ptype jmisc
> type = class jmisc  extends java.lang.Object {
>
>     void main__5jmisc_ZN5jmisc4mainEP6JArrayIPN4java4lang6StringEE;
>     void _ZN5jmiscC1Ev;
> }
>
> The stabs data refers to this correctly mangled symbol...
>
> _ZN5jmisc4mainEP6JArrayIPN4java4lang6StringEE
>
> So how does the physname get the "main__5jmisc" prefix?
 From the fun way we extract type info off of methods, in STABS, of 
course!
breakpoint on parse_and_eval_type or something like that, and you'll see 
it happen.

> The full
> main__5jmisc_ZN5jmisc4mainEP6JArrayIPN4java4lang6StringEE string is
> passed to the v3 demangler, which doesn't recognize it and assumes it
> is a C symbol.
>
> Any ideas?
>
> Thanks,
>
> AG
>