An executable produced by clang can not be debuggedwith gdb under Windows

Yes I mean that I use "-target i386-pc-mingw32" option to use Mingw headers and ABI.

But I don't think this gdb debug problem is about mingw.

I think it is clang's problem.

Does "clang r153589" newer than "clang 3.1"?

======= 2012-10-24 11:04:50 ÄúÔÚÀ´ÐÅÖÐдµÀ£º=======

I don't understand what you mean by "use Clang... with MinGW"? Clang
compiled with Visual Studio acts as a native windows compiler (msvc
replacement and targets MS ABI). Use the i386-pc-mingw32 triple to
tell Clang to use Mingw headers and ABI. If that doesn't help you
could try using MinGW 4.6 because I remember seeing other issues with
4.7. Hope this helps.

Hi All:

        I use Windows 7 32bit, and I build Clang 3.1 with MS VS2008.

        I use Clang to build "hello world" C program with MinGW32 4.7.0 by "clang.exe main.c -g -o main.exe".

        Then I use gdb 6.8 to debug my exe and I get this info:

    "DW_FORM_strp pointing outside of .debug_str section"

        I find http://llvm.org/bugs/show_bug.cgi?id=13636 bug report, but there is no solution.

        And http://llvm.org/bugs/show_bug.cgi?id=11898 bug repor refer to "clang r153589", how can I get this version.

        Thanks!

¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡fiveight
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡fiveight@tom.com
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2012-10-24

_______________________________________________
cfe-dev mailing list
cfe-dev@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev

= = = = = = = = = = = = = = = = = = = =
      
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ÖÂ
Àñ£¡

¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡fiveight
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡fiveight@tom.com
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2012-10-24

I think that clang --version gives the exact revision number?

Yes I mean that I use "-target i386-pc-mingw32" option to use Mingw headers and ABI.

I only saw the "clang.exe main.c -g -o main.exe" command, you forgot
to mention the triple. So we can probably rule this out since you're
using the right triple.

But I don't think this gdb debug problem is about mingw.

Me neither.

I think it is clang's problem.

You're probably right, but as I said, there were some issues with
clang + mingw 4.7 combo. Try mingw 4.6.2 if it's not too much of a
problem for you. I never managed to get clang going with 4.7, and
haven't really bothered again.