Summary: | Emit debug information about non-type template parameters | ||
---|---|---|---|
Product: | gcc | Reporter: | Wolfgang Bangerth <bangerth> |
Component: | c++ | Assignee: | Not yet assigned to anyone <unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | dodji, gcc-bugs, jkratochvil, tromey |
Priority: | P3 | ||
Version: | 3.2 | ||
Target Milestone: | --- | ||
Host: | Target: | ||
Build: | Known to work: | ||
Known to fail: | Last reconfirmed: | 2005-12-11 23:03:15 | |
Bug Depends on: | 30161 | ||
Bug Blocks: |
Description
Wolfgang Bangerth
2002-09-16 10:56:00 UTC
still exitst on the mainline (20030525). tin:~/src/gnu/gcctest>gcc -g3 pr7932.cc tin:~/src/gnu/gcctest>gdb a.out GNU gdb 2003-05-24-cvs Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"... (gdb) run Starting program: /home/gates/pinskia/src/gnu/gcctest/a.out Program received signal SIGABRT, Aborted. 0x420292d1 in kill () from /lib/i686/libc.so.6 (gdb) fr 3 #3 0x08048361 in X (this=0xbffec587) at pr7932.cc:5 5 X(){ abort(); }; (gdb) p dim No symbol "dim" in current context. I think this bug should be fixed in trunk (4.5) by the patch for PR debug/30161. Can we close this bug or should we wait for GDB ? (In reply to comment #2) > I think this bug should be fixed in trunk (4.5) by the patch for PR > debug/30161. > Can we close this bug or should we wait for GDB ? What does GDB currently say for the testcase shown in the initial report? W. Subject: Re: Emit debug information about non-type template
parameters
Le 01/09/2009 00:05, bangerth at gmail dot com a écrit :
> What does GDB currently say for the testcase shown in the initial report?
I think GDB doesn't know about the new type debug information added by gcc
yet. So it won't say anything. But I haven't test GDB HEAD. My reasoning
was that maybe we could open a GDB bug to track this there now that we
generate debug info for this case ? Or is there a GDB bug opened for this
already ?
(In reply to comment #4) > > What does GDB currently say for the testcase shown in the initial report? > > I think GDB doesn't know about the new type debug information added by gcc > yet. So it won't say anything. I just tried with GDB 6.6, and you are right: it doesn't know about "dim". > But I haven't test GDB HEAD. My reasoning > was that maybe we could open a GDB bug to track this there now that we > generate debug info for this case ? Or is there a GDB bug opened for this > already ? I didn't open a GDB bug back then, and I don't have any experience with GDB bugs in the first place. Would you mind opening a bug with their bugzilla (or whatever they use)? Either way, yes, we can close this PR now. Thanks W. |