Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Fabian Cenedese <Cenedese@indel.ch>
To: gdb@sourceware.org
Subject: Path problem with dwarf on cygwin
Date: Wed, 29 Nov 2006 15:40:00 -0000	[thread overview]
Message-ID: <5.2.0.9.1.20061129160827.0189b8d0@NT_SERVER> (raw)

Hi

I have another problem. This is again with gcc 4.1.0 and gdb 6.5 both
configured as host=cygwin, target=ppc-eabi (not literally :)

If I compile my project with -gstabs I don't seem to have any problems.
There are some warnings when I load the file but I can work with it.
But with dwarf debug info gdb has quite some problems resolving
files.

stabs:
Reading symbols from /data/gdb-6.5/gdb/gccext3-41s.x...
unknown symbol type 0x1e...expanding to full symbols...couldn't parse type; debu
gger out of date?...block end address less than block start address in fixed32::
fixed32(short, unsigned short) (patched it)...inner block (0xa8e58-0xa8e58) not
inside outer block (0x21d0-0x70950)...inner block not inside outer block in CINO
SModule::CINOSModule(long, char*, char*, char*, char*, char*, char*, char*, char
*, char*)...done.

(gdb) info line N:\Indel-PPC\Tests\gccext3\applicat\src\CTaskTemplateClass.cpp:142
Line 142 of "N:\Indel-PPC\Tests\gccext3\applicat\src\CTaskTemplateClass.cpp"
   starts at address 0xebd8 <_ZN17_TASK_CLASS_NAME_6ActionEv+184>
   and ends at 0xebdc <_ZN17_TASK_CLASS_NAME_D0Ev>.

dwarf:
Reading symbols from /data/gdb-6.5/gdb/gccext3-41d.x...unknown symbol type 0x1e.
..expanding to full symbols...Location list used without specifying the CU base
address....unsupported const value attribute form: 'DW_FORM_strp'...done.

(gdb) info line N:\Indel-PPC\Tests\gccext3\applicat\src\CTaskTemplateClass.cpp:142
Line number 142 is out of range for "N:\Indel-PPC\Tests\gccext3\applicat\src\CTaskTemplateClass.cpp".
(gdb) info line N:\Indel-PPC\Tests\gccext3\applicat\src/CTaskTemplateClass.cpp:142
Line number 142 is out of range for "N:\Indel-PPC\Tests\gccext3\applicat\src\CTaskTemplateClass.cpp".
(Other combinations of / and \ didn't work either).

After dumping all symbols I found that I have two symtabs for this file, one
has a linetable, the other does not. The only difference is the last path separator.

Symtab for file N:\Indel-PPC\Tests\gccext3\applicat\src\CTaskTemplateClass.cpp
Language: c++

Blockvector:
...

Symtab for file N:\Indel-PPC\Tests\gccext3\applicat\src/CTaskTemplateClass.cpp
Language: c++
Line table:
...
line 142 at 0xebd8
...
Blockvector same as previous symtab

How can this happen? Is this a problem of gcc or gdb? As I call gcc directly,
not from inside the cygwin shell, I give all paths with backslashes. So why is
there one with a forward slash?

Is there a possibility to tell gdb that these are the same files and not
create two symtabs? Or maybe a flag for configure of gcc/gdb? Something
like the textmode.o module for cygwin compiled programs.

Thanks

bye  Fabi



             reply	other threads:[~2006-11-29 15:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-29 15:40 Fabian Cenedese [this message]
2006-11-29 15:43 ` Daniel Jacobowitz
2006-11-29 16:12   ` Fabian Cenedese
2006-11-29 16:13     ` Daniel Jacobowitz
2006-11-29 16:24       ` Fabian Cenedese
2006-11-29 18:39   ` Eli Zaretskii
2006-11-29 19:05     ` Daniel Jacobowitz

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.20061129160827.0189b8d0@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