From: Fabian Cenedese <Cenedese@indel.ch>
To: gdb@sourceware.org
Subject: symbol maintenance
Date: Fri, 24 Nov 2006 13:44:00 -0000 [thread overview]
Message-ID: <5.2.0.9.1.20061124142829.017493c0@NT_SERVER> (raw)
Hello
After loading a file (without starting anything) I tried "maintenance check-symbols".
I got lots of messages like:
Global symbol `__7fixed32' only found in ..(path)..\Inos_typ.cpp psymtab
Global symbol `IntOf__7fixed64' only found in ..(path)..\Inos_typ.cpp psymtab
Global symbol `__7fixed64' only found in ..(path)..\Inos_typ.cpp psymtab
Global symbol `__ml__FG7fixed32T0' only found in ..(path)..\Inos_typ.cpp psymtab
Global symbol `__ml__FG7fixed64T0' only found in ..(path)..\Inos_typ.cpp psymtab
Is this something to worry about? Does this indicate wrong debug info or an
error in gdb? If it's nothing to worry about what's the use of these messages?
Only for gdb interna?
This is a gdb 6.5 cross-compiled with cygwin on WinXP for ppc.
I:\cyghome\data\gdb-6.5\gdb>gdb --readnow
GNU gdb 6.5
..(GPL)...
This GDB was configured as "--host=i686-pc-cygwin --target=powerpc-eabi".
Setting up the environment for debugging gdb.
No symbol table is loaded. Use the "file" command.
No symbol table is loaded. Use the "file" command.
/data/gdb-6.5/gdb/.gdbinit:8: Error in sourced command file:
No breakpoint number 0.
(gdb) file gccext3.x
Reading symbols from /data/gdb-6.5/gdb/gccext3.x...unknown symbol type 0x1e...ex
panding to full symbols...unsupported const value attribute form: 'DW_FORM_strin
g'...const value length mismatch for 'ciOffline', got 8, expected 0...done.
Are these warnings something to worry about?
Thanks
bye Fabi
next reply other threads:[~2006-11-24 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 13:44 Fabian Cenedese [this message]
2006-11-27 21:30 ` Jim Blandy
2006-11-28 11:39 ` Fabian Cenedese
2006-11-28 19:42 ` Jim Blandy
2006-11-29 9:24 ` Fabian Cenedese
2006-11-29 10:55 ` Fabian Cenedese
2006-11-29 11:04 ` Fabian Cenedese
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=5.2.0.9.1.20061124142829.017493c0@NT_SERVER \
--to=cenedese@indel.ch \
--cc=gdb@sourceware.org \
/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