Thread overview | ||||||
---|---|---|---|---|---|---|
|
April 23, 2005 gdb and D | ||||
---|---|---|---|---|
| ||||
Hi, I am using gdc for a while now. I was never able to use gdb in combination with D, which makes it hard to debug segfaults. When I invoke gdb on a d executable I get: ../../gdb-6.3/gdb/dwarf2read.c:5446: internal-error: could not find partial DIE in cache Although I can continue the debugging session there are a lot warnings about missing debug symbols and I can't get any information from backtraces since they seem to contain only garbage, at least I can't explain why there are several calls to 0x00000000 :) I tried gdb on dmd, gdc 0.10 and 0.11pre1 (with gcc-3.4.3) executables. gdb version is 6.3, I used the debian version and after this didn't work I recompiled a clean gdb-6.3 using the fresh compiled gcc-3.4.3 which didn't work too. Has someone had the same error and was able to resolve it? Any hints are appreciated. Regards - Torben |
April 23, 2005 Re: gdb and D | ||||
---|---|---|---|---|
| ||||
On Sat, 23 Apr 2005 09:18:35 +0200, Thomas Kuehne wrote: > gdb-6.0-2mdk (the official Mandrake build) has works most of the times. I tried gdb 6.0 and it works out of the box. > Did you "make test" when you recompiled gdb 6.3? There is no "test" target :( Just to make sure that I am not stupid, I compiled 6.3 the same way I compiled 6.0 just now. Fortunately it still doesn't work :) Thanks - Torben |
April 23, 2005 Re: gdb and D | ||||
---|---|---|---|---|
| ||||
Posted in reply to Torben Gleich | -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Torben Gleich schrieb am Sat, 23 Apr 2005 09:10:23 +0200: > Hi, > > I am using gdc for a while now. I was never able to use gdb in combination with D, which makes it hard to debug segfaults. > > When I invoke gdb on a d executable I get: > > ../../gdb-6.3/gdb/dwarf2read.c:5446: internal-error: could not find partial DIE in cache > > Although I can continue the debugging session there are a lot warnings about missing debug symbols and I can't get any information from backtraces since they seem to contain only garbage, at least I can't explain why there are several calls to 0x00000000 :) > > I tried gdb on dmd, gdc 0.10 and 0.11pre1 (with gcc-3.4.3) executables. gdb version is 6.3, I used the debian version and after this didn't work I recompiled a clean gdb-6.3 using the fresh compiled gcc-3.4.3 which didn't work too. > > Has someone had the same error and was able to resolve it? Any hints are appreciated. gdb-6.0-2mdk (the official Mandrake build) works most of the time. Did you "make test" when you recompiled gdb 6.3? Thomas -----BEGIN PGP SIGNATURE----- iD8DBQFCafxd3w+/yD4P9tIRArfdAJwPcnY5c2ptdsoxBYBAhUB0pNDPVwCfY2ty 9PtoGSJa7N3KtDNt/k6lQ68= =kkoh -----END PGP SIGNATURE----- |
April 23, 2005 Re: gdb and D | ||||
---|---|---|---|---|
| ||||
Posted in reply to Torben Gleich | -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Torben Gleich schrieb am Sat, 23 Apr 2005 09:39:37 +0200: > On Sat, 23 Apr 2005 09:18:35 +0200, Thomas Kuehne wrote: > >> gdb-6.0-2mdk (the official Mandrake build) has works most of the times. > > I tried gdb 6.0 and it works out of the box. > >> Did you "make test" when you recompiled gdb 6.3? > > There is no "test" target :( sorry "make check". Thomas -----BEGIN PGP SIGNATURE----- iD8DBQFCafyX3w+/yD4P9tIRApyhAJ9C8AEc9PjItu42mDHyjBL6BllJBgCguShg uLejSuQYADMKCQZhai3S9DA= =iDGT -----END PGP SIGNATURE----- |
Copyright © 1999-2021 by the D Language Foundation