search for: gdb1

I'm having trouble debugging x86 code generated by LLVM. GDB does work with the code, but not correctly, for example, the "next" command does not skip over a function call. Here's an example. Source program gdb1.c: int x; void foo(){ x++; } void bar(){ x--; } int main(){ foo(); bar(); return 0; } commands: $ llvm-gcc -g -emit-llvm -c gdb1.c -o gdb1.bc $ llc gdb1.bc $ gcc -m32 gdb1.s -o gdb1 $ gdb ./gdb1 GNU gdb Red Hat Linux (6.6-16.fc7rh) Copyright (C) 2006 Free Software Foundation, Inc....

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 D...

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...

Well... $ ~/software/llvm-gcc4.2-2.5-x86-linux-RHEL4/bin/llvm-gcc -g gdb1.c -o gdb1 /tmp/ccbAj8x9.s: Assembler messages: /tmp/ccbAj8x9.s:35: Error: suffix or operands invalid for `push' /tmp/ccbAj8x9.s:44: Error: suffix or operands invalid for `pop' /tmp/ccbAj8x9.s:56: Error: suffix or operands invalid for `push' /tmp/ccbAj8x9.s:65: Error: suffix or operands...

On Apr 20, 2009, at 5:06 PMPDT, Ken McMillan wrote: > > Well... > > $ ~/software/llvm-gcc4.2-2.5-x86-linux-RHEL4/bin/llvm-gcc -g gdb1.c - > o gdb1 > /tmp/ccbAj8x9.s: Assembler messages: > /tmp/ccbAj8x9.s:35: Error: suffix or operands invalid for `push' > /tmp/ccbAj8x9.s:44: Error: suffix or operands invalid for `pop' > /tmp/ccbAj8x9.s:56: Error: suffix or operands invalid for `push' > /tmp/ccbAj8x9....

Hi Ken, Ken McMillan wrote: > I'm having trouble debugging x86 code generated by LLVM. > GDB does work with the code, but not correctly, for example, > the "next" command does not skip over a function call. > > Here's an example. > > Source program gdb1.c: > > int x; > > void foo(){ > x++; > } > > void bar(){ > x--; > } > > int main(){ > foo(); > bar(); > return 0; > } > > commands: > > $ llvm-gcc -g -emit-llvm -c gdb1.c -o gdb1.bc > $ llc gdb1.bc > Try llc -disable-f...

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...

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 the job of most optimizations is to change the code from something that corr...

...ALG8, ALG9, AMS1, ANP1, ARA1, ATH1, BCH1, BCH2, BMH1, BMH2, BNI4, BUD7, CAX4, CDC19, CHS3, CHS5, CHS6, CHS7, CIT2, CTS1, CWH41, DDP1, DIE2, DIP5, DLD1, DOG1, DOG2, DPM1, ELM1, ENO1, ENO2, EOS1, ERD1, EXG1, FBA1, FBP1, FBP26, FDH1, FKS1, GAC1, GAL1, GAL10, GAL2, GAL3, GAL4, GAL7, GAL80, GCY1, GDA1, GDB1, GFA1, GIP2, GLC3, GLC7, GLC8, GLG1, GLG2, GLK1, GLO2, GLO4, GNA1, GND1, GND2, GNT1, GPH1, GPM1, GRE3, GSC2, GSY1, GSY2, GTB1, GUT2, HAP4, HKR1, HOC1, HOR2, HPF1, HXK1, HXK2, HXT4, ICL1, IMP2', INM1, INM2, ITR1, KAR2, KEG1, KNH1, KRE2, KRE5\nc:ABC1") > read.table("tst1", sep=&...

...ONF ID=002 #0x0005 LEN=0014 Controller/PLCI/NCCI = 0x10101 Info = 0x0 Speicherzugriffsfehler (core dumped) srvpbx:/usr/src/chan-capi-trunk# -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: gdb1.txt Url: http://lists.digium.com/pipermail/asterisk-users/attachments/20100309/a08e9a33/attachment.txt