[LLVMdev] Possibility of Corruption of debug metadata

[shankha]

Hi Devang,

On Wed, Oct 13, 2010 at 12:44 PM, Devang Patel <dpatel at apple.com> wrote:
> In your example, you do not need to update debug info for @global_var at the moment. We are not identifying tls in debug info yet.

Does that mean I will not be able to debug applications which use tls
through gdb if they are  build with gcc-lllvm or clang.

> On Oct 13, 2010, at 8:30 AM, shankha wrote:
>
>> I do not face any issues debugging my test case. But while debugging
>> my application
>> through gdb I cannot make sense of the call stack. I do not see the
>> function names in
>> the call stack (with or without insertion of additional function calls
>> or local variables).
>
> What is the difference between your test case and application ? Is your application compiled using same compiler options ?

   My application is the linux kernel TCP/IP stack layer. There are
few #defines and compiler options which are different. Such as
 -D"KBUILD_STR(s)=#s" -D"KBUILD_MODNAME=KBUILD_STR()" -D__KERNEL__,
-fno-common -fno-strict-aliasing.

Are these options in any way responsible for the problems I am facing
while debugging.
At this moment it is not possible for me to run my application
standalone without
modifying it.


Thanks for your help.
> -
> Devang



-- 
Thanks
Shankha Banerjee