search for: impact2

...ditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu"... Using host libthread_db library "/lib64/libthread_db.so.1". (gdb) b main Breakpoint 1 at 0x80483a0: file /home/mcmillan/projects/impact2/test//gdb1.c, line 11. (gdb) run Starting program: /home/mcmillan/projects/impact2/test/gdb1 Breakpoint 1, main () at /home/mcmillan/projects/impact2/test//gdb1.c:11 11 int main(){ (gdb) next main () at /home/mcmillan/projects/impact2/test//gdb1.c:12 12 foo(); (gdb) foo () at /home/mcmillan/pr...

I see. Here's another interesting issue: (gdb) b gdb1.c:4 No line 4 in file "gdb1.c". (gdb) step foo () at /home/mcmillan/projects/impact2/test//gdb1.c:4 4 x++; (gdb) You can see that I can step to line 4, but I can't set a breakpoint there. (I used -disable-fp-elim in the compilation). Have you seen this before? Thanks -- Ken Dale Johannesen wrote: > > > On Apr 14, 2009, at 4:19 PMPDT, Ken McMillan wrote: >...

Ken McMillan wrote: > I see. Here's another interesting issue: > > (gdb) b gdb1.c:4 > No line 4 in file "gdb1.c". > (gdb) step > foo () at /home/mcmillan/projects/impact2/test//gdb1.c:4 > 4 x++; > (gdb) > > You can see that I can step to line 4, but I can't set a breakpoint there. > Works fine here (llvm 2.5, 32 bit, gdb 6.8) Try llc -disable-fp-elim -fast gdb1.bc If you do llvm-gcc -g gdb1.c -o gdb1 does it have the same issue ? -Arg...

...g gdb 6.6. Will try 6.8... Thanks -- Ken Argiris Kirtzidis wrote: > > Ken McMillan wrote: >> I see. Here's another interesting issue: >> >> (gdb) b gdb1.c:4 >> No line 4 in file "gdb1.c". >> (gdb) step >> foo () at /home/mcmillan/projects/impact2/test//gdb1.c:4 >> 4 x++; >> (gdb) >> >> You can see that I can step to line 4, but I can't set a breakpoint >> there. >> > > Works fine here (llvm 2.5, 32 bit, gdb 6.8) > > Try > > llc -disable-fp-elim -fast gdb1.bc > > If yo...

Argiris Kirtzidis wrote: > > ... > > Try > llc -disable-fp-elim gdb1.bc > > Thanks, I would never have guessed that :-). Are there any other optimizations that are harmful to debug info that I should know about? Thanks -- Ken -- View this message in context: http://www.nabble.com/problems-with-dwarf-gdb-tp23033690p23049871.html Sent from the LLVM - Dev mailing list

On Apr 14, 2009, at 4:19 PMPDT, Ken McMillan wrote: > > > > Argiris Kirtzidis wrote: >> >> ... >> >> Try >> llc -disable-fp-elim gdb1.bc >> >> > > Thanks, I would never have guessed that :-). > > Are there any other optimizations that are harmful to > debug info that I should know about? Lots of them. Partly this is because

...gt; > > Argiris Kirtzidis wrote: >> >> Ken McMillan wrote: >>> I see. Here's another interesting issue: >>> >>> (gdb) b gdb1.c:4 >>> No line 4 in file "gdb1.c". >>> (gdb) step >>> foo () at /home/mcmillan/projects/impact2/test//gdb1.c:4 >>> 4 x++; >>> (gdb) >>> >>> You can see that I can step to line 4, but I can't set a breakpoint >>> there. >>> >> >> Works fine here (llvm 2.5, 32 bit, gdb 6.8) >> >> Try >> >> llc -disab...