Re: [llvm-commits] CVS: llvm/test/DebugInfo/2006-11-06-StackTrace.cpp
Are you sure that's the problem? Even on my machine, where the OS
identifies the hardware as amd64, the test was correctly XFAILing.
Chris Lattner wrote:
Changes in directory llvm/test/DebugInfo:
2006-11-06-StackTrace.cpp updated: 1.11 - 1.12
---
Log message:
fix failure on ahs3's tester
---
Diffs of the changes: (+3 -1)
2006-11-06-StackTrace.cpp |4 +++-
1 files changed, 3 insertions(+), 1 deletion(-)
Index: llvm/test/DebugInfo/2006-11-06-StackTrace.cpp
diff -u llvm/test/DebugInfo/2006-11-06-StackTrace.cpp:1.11
llvm/test/DebugInfo/2006-11-06-StackTrace.cpp:1.12
--- llvm/test/DebugInfo/2006-11-06-StackTrace.cpp:1.11Sun Apr 15
17:37:04 2007
+++ llvm/test/DebugInfo/2006-11-06-StackTrace.cpp Sat May 5 15:50:35 2007
@@ -8,7 +8,9 @@
// RUN: grep {#0 DeepStack::deepest.*(this=.*,.*x=33)}
// RUN: gdb -q -batch -n -x %t.in %t.exe | \
// RUN: grep {#7 0x.* in main.*(argc=\[12\],.*argv=.*)}
-// XFAIL: i[1-9]86|alpha|ia64|arm|x86_64
+
+// Only works on ppc. Should generalize?
+// XFAIL: i[1-9]86|alpha|ia64|arm|x86_64|amd64
#include stdlib.h
___
llvm-commits mailing list
llvm-commits@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
___
llvm-commits mailing list
llvm-commits@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
Re: [llvm-commits] CVS: llvm/test/DebugInfo/2006-11-06-StackTrace.cpp
On May 5, 2007, at 2:03 PM, Jeff Cohen wrote:
Are you sure that's the problem? Even on my machine, where the OS
identifies the hardware as amd64, the test was correctly XFAILing.
No, I'm not sure. A better question is: why is this ppc specific? :)
-Chris
Chris Lattner wrote:
Changes in directory llvm/test/DebugInfo:
2006-11-06-StackTrace.cpp updated: 1.11 - 1.12
---
Log message:
fix failure on ahs3's tester
---
Diffs of the changes: (+3 -1)
2006-11-06-StackTrace.cpp |4 +++-
1 files changed, 3 insertions(+), 1 deletion(-)
Index: llvm/test/DebugInfo/2006-11-06-StackTrace.cpp
diff -u llvm/test/DebugInfo/2006-11-06-StackTrace.cpp:1.11 llvm/
test/DebugInfo/2006-11-06-StackTrace.cpp:1.12
--- llvm/test/DebugInfo/2006-11-06-StackTrace.cpp:1.11 Sun Apr 15
17:37:04 2007
+++ llvm/test/DebugInfo/2006-11-06-StackTrace.cppSat May 5
15:50:35 2007
@@ -8,7 +8,9 @@
// RUN: grep {#0 DeepStack::deepest.*(this=.*,.*x=33)}
// RUN: gdb -q -batch -n -x %t.in %t.exe | \
// RUN: grep {#7 0x.* in main.*(argc=\[12\],.*argv=.*)}
-// XFAIL: i[1-9]86|alpha|ia64|arm|x86_64
+
+// Only works on ppc. Should generalize?
+// XFAIL: i[1-9]86|alpha|ia64|arm|x86_64|amd64
#include stdlib.h
___
llvm-commits mailing list
llvm-commits@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
___
llvm-commits mailing list
llvm-commits@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
___
llvm-commits mailing list
llvm-commits@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
Re: [llvm-commits] CVS: llvm/test/DebugInfo/2006-11-06-StackTrace.cpp
Chris Lattner wrote: On May 5, 2007, at 2:03 PM, Jeff Cohen wrote: Are you sure that's the problem? Even on my machine, where the OS identifies the hardware as amd64, the test was correctly XFAILing. No, I'm not sure. A better question is: why is this ppc specific? :) -Chris On my machine, anyway, the gdb stack trace shows that the debugging info is basically garbage. ___ llvm-commits mailing list llvm-commits@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
Re: [llvm-commits] CVS: llvm/test/DebugInfo/2006-11-06-StackTrace.cpp
On May 5, 2007, at 2:49 PM, Jeff Cohen wrote: Chris Lattner wrote: On May 5, 2007, at 2:03 PM, Jeff Cohen wrote: Are you sure that's the problem? Even on my machine, where the OS identifies the hardware as amd64, the test was correctly XFAILing. No, I'm not sure. A better question is: why is this ppc specific? :) -Chris On my machine, anyway, the gdb stack trace shows that the debugging info is basically garbage. Ok, then it really is failing. -Chris ___ llvm-commits mailing list llvm-commits@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
Re: [llvm-commits] CVS: llvm/test/DebugInfo/2006-11-06-StackTrace.cpp
Ok, then it really is failing. Same here. This is strange, however I haven't tested debug information on C++ programs. Will try to look. -- With best regards, Anton Korobeynikov. Faculty of Mathematics Mechanics, Saint Petersburg State University. ___ llvm-commits mailing list llvm-commits@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
Re: [llvm-commits] CVS: llvm/test/DebugInfo/2006-11-06-StackTrace.cpp
Chris Lattner wrote:
On May 5, 2007, at 2:49 PM, Jeff Cohen wrote:
Chris Lattner wrote:
On May 5, 2007, at 2:03 PM, Jeff Cohen wrote:
Are you sure that's the problem? Even on my machine, where the OS
identifies the hardware as amd64, the test was correctly XFAILing.
No, I'm not sure. A better question is: why is this ppc specific? :)
-Chris
On my machine, anyway, the gdb stack trace shows that the debugging
info is basically garbage.
Ok, then it really is failing.
-Chris
This is the output on my machine. It looks better than when I last
looked at it, but still leaves a lot to be desired.
Breakpoint 1 at 0x4007d0: file 2006-11-06-StackTrace.cpp, line 27.
Breakpoint 1, DeepStack::deepest (this=0x7fffe6c8, x=27) at
2006-11-06-StackTrace.cpp:27
27int deepest ( int x ) { return x + 7; }
#0 DeepStack::deepest (this=0x7fffe6c8, x=27) at
2006-11-06-StackTrace.cpp:27
#1 0x00400821 in DeepStack::deeper (this=0x7fffe6c8, x=27)
at 2006-11-06-StackTrace.cpp:26
#2 0x1f927800 in ?? ()
#3 0x1f90949a in find_symdef () from /libexec/ld-elf.so.1
#4 0x00400881 in DeepStack::shallow (this=0x1fe7ca92, x=0) at
2006-11-06-StackTrace.cpp:24
#5 0x1feee2f0 in strcspn () from /lib/libc.so.6
#6 0x1f927800 in ?? ()
#7 0x00140002 in ?? ()
#8 0x7fffe6c8 in ?? ()
#9 0x7fffe660 in ?? ()
#10 0x004008b1 in DeepStack::shallower (this=0x1fe7ca92, x=0) at
2006-11-06-StackTrace.cpp:23
#11 0x0246 in ?? ()
#12 0x in ?? ()
#13 0x0012001c in ?? ()
#14 0x7fffe6c8 in ?? ()
#15 0x7fffe690 in ?? ()
#16 0x004008e0 in DeepStack::shallowest (this=0x1fe7ca92, x=0)
at 2006-11-06-StackTrace.cpp:22
#17 0x in ?? ()
#18 0x0002 in ?? ()
#19 0x0011e6f0 in ?? ()
#20 0x7fffe6c8 in ?? ()
#21 0x7fffe6b0 in ?? ()
#22 0x00400909 in DeepStack::runit (this=0x1fe7ca92) at
2006-11-06-StackTrace.cpp:29
#23 0x0011 in ?? ()
#24 0x7fffe6c8 in ?? ()
#25 0x7fffe6f0 in ?? ()
#26 0x00400757 in main (argc=0, argv=0x1fe7ca72) at
2006-11-06-StackTrace.cpp:35
___
llvm-commits mailing list
llvm-commits@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
Re: [llvm-commits] CVS: llvm/test/DebugInfo/2006-11-06-StackTrace.cpp
Jeff, This is the output on my machine. It looks better than when I last looked at it, but still leaves a lot to be desired. Could you please send me output from your native compiler. Something like 'gcc -g -O0 -S -dA foo.c' should be enough. -- With best regards, Anton Korobeynikov. Faculty of Mathematics Mechanics, Saint Petersburg State University. ___ llvm-commits mailing list llvm-commits@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
