[LLVMdev] LLVM Compiler Infrastructure and GDB debugger

Chris Lattner sabre at nondot.org
Fri Jun 26 11:33:04 PDT 2009

Hi Artem,

GDB only works with native applications.  If you compile your code to  
a native executable with -g, then debug info should work for you.   
However, if you've built your own backend, then you may need to add  
the debug info hooks etc.  If you have further questions, please email  
the llvmdev mailing list instead of me directly, thanks!


On Jun 26, 2009, at 11:11 AM, Rudskyy wrote:

> Hallo, Chris Lattner!
> I have found you in LLVM Developers page (http://llvm.org/developers.cgi 
> ).
> First thank you for all of your work with LLVM.
> About:
> I work with the LLVM Compiler Infrastructure to implement a backend  
> for specific processor xPEC of chip NetX (http://hilscher.com/netx..html 
> ).
> So C-code already possible compile to the native xPEC assembly code  
> (works perfect! LLWM a big power!).
> Now I need to debug the source C-code, that I compile for xPEC- 
> processor. I have read the article “Source Level Debugging with  
> LLVM” (http://llvm.org/docs/SourceLevelDebugging.html), where were  
> described that is possible to use debugger GDB. Wonderful! I have  
> found much information about GDB (of course http://sourceware.org/ 
> gdb/ ) and it has a debugging of remote programs.
> Problem:
> I don’t understand how must be compiled the C-code with “llvm-gcc”.  
> Wenn I use option “-emit-llvm” [backend needs it] of course with “- 
> g” and “-O0”,  then GDB can’t find a symbol table in bc-file.  Where  
> will place “llvm-gcc” the symbol table for DGB? Perhaps, must GDB  
> knows the architecture of processor? If yes, so where it must be  
> written?   I have many questions and need some help.
> Do you can help me what must I read and search ore recommend  
> somebody to can?
> Best regards,
> Artem Rudskyy
> http://www..uni-magdeburg.de/ieat/robotslab/
> http://www.uni-magdeburg.de/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090626/1f7b1eb1/attachment.html>

More information about the llvm-dev mailing list