From: Daniel Berlin <dberlin@redhat.com>
To: "Peter.Schauer" <Peter.Schauer@regent.e-technik.tu-muenchen.de>
Cc: msnyder@cygnus.com, jimb@cygnus.com,
gdb-patches@sources.redhat.com, ezannoni@cygnus.com
Subject: Re: [RFA]: Fix partial symbol lookups
Date: Thu, 16 Nov 2000 09:16:00 -0000 [thread overview]
Message-ID: <m38zqj25xy.fsf@dan2.cygnus.com> (raw)
In-Reply-To: <200011161706.SAA06577@reisser.regent.e-technik.tu-muenchen.de>
"Peter.Schauer" <Peter.Schauer@regent.e-technik.tu-muenchen.de> writes:
> > No, I'll clean it up if you like. Assuming you don't want me to just
> > revert all the 10-12 changes and be done with it.
>
> This decision has to be made by the symtab maintainers of course.
Sure, but i'd appreciate a friendly opinion as to whether these
patches have any hope or not.
>
> > > No, it points out another problem with `maint check'. Have you ever tried it
> > > with your patches ?
> >
> > Yes, I have.
> > (gdb) maintenance check-symtabs
> > During symbol reading, type qualifier 'const' ignored.
> > During symbol reading, unsupported stack op: 'DW_OP_deref_size'.
> > During symbol reading, type qualifier 'volatile' ignored.
> > (gdb)
>
> Well, with gcc-2.95.2 -ggdb on a linux x86 box I get
>
> (gdb) maint check
> During symbol reading, type qualifier 'const' ignored.
> During symbol reading, type qualifier 'volatile' ignored.
> During symbol reading, type qualifier 'const' ignored.
> Global symbol `__24Contains_static_instanceii' only found in misc.cc psymtab
> Global symbol `__31Contains_nested_static_instanceii' only found in misc.cc psym
> tab
> Global symbol `__3Bariii' only found in misc.cc psymtab
> Global symbol `__3Fooii' only found in misc.cc psymtab
> Global symbol `__5Base1i' only found in misc.cc psymtab
> Global symbol `__Q231Contains_nested_static_instance6Nestedi' only found in misc
> .cc psymtab
> Global symbol `__opi__3Foo' only found in misc.cc psymtab
> Global symbol `foo__C22const_vol_method_classRi' only found in misc.cc psymtab
> Global symbol `times__3Fooi' only found in misc.cc psymtab
>
> which is not surprising, because maintenance_check_symtabs calls
> lookup_block_symbol with the mangled symbol name.
> Perhaps you have applied more patches to your source tree...
Hmmmm.
Weird.
I am using a different gcc, but this shouldn't account for it.
--Dan
next prev parent reply other threads:[~2000-11-16 9:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3snorj4d7.fsf@dan2.cygnus.com>
2000-11-16 8:29 ` Peter.Schauer
2000-11-16 8:44 ` Daniel Berlin
2000-11-16 9:06 ` Peter.Schauer
2000-11-16 9:16 ` Daniel Berlin [this message]
2000-11-16 8:56 ` Daniel Berlin
2000-11-16 9:02 ` Daniel Berlin
[not found] <200011161222.NAA05985@reisser.regent.e-technik.tu-muenchen.de>
[not found] ` <m38zqj3mcb.fsf@dan2.cygnus.com>
2000-11-16 11:01 ` Christopher Faylor
[not found] <m3vgtqv60a.fsf@dan2.cygnus.com>
[not found] ` <npbsvhzxm9.fsf@zwingli.cygnus.com>
[not found] ` <m3hf59izpl.fsf@dan2.cygnus.com>
2000-11-15 8:56 ` Michael Snyder
[not found] ` <m3g0ktkrjh.fsf@dan2.cygnus.com>
2000-11-15 11:19 ` Michael Snyder
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=m38zqj25xy.fsf@dan2.cygnus.com \
--to=dberlin@redhat.com \
--cc=Peter.Schauer@regent.e-technik.tu-muenchen.de \
--cc=ezannoni@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@cygnus.com \
--cc=msnyder@cygnus.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