search

Quuxplusone / LLVMBugzillaTest

0 stars 0 forks source link

no debugging symbols found in gdb when assembly file is compiled to form the executable with -g option. #12298

Open Quuxplusone opened 12 years ago

Quuxplusone commented 12 years ago
Bugzilla Link PR12922
Status NEW
Importance P normal
Reported by Mayur (mayurthebond@gmail.com)
Reported on 2012-05-23 10:33:19 -0700
Last modified on 2012-08-18 12:00:12 -0700
Version unspecified
Hardware PC Linux
CC anton@korobeynikov.info, eran.ifrah@gmail.com, llvm-bugs@lists.llvm.org
Fixed by commit(s)
Attachments thumb2-it.S (3999 bytes, text/plain)
Blocks
Blocked by
See also 
I have an assembly file containing thumb2-it(thumb2 IF THEN) instructions which
i need to check for single step in gdb. The problem being faced is that when i
am compiling this assembly .S file using clang with -g option and running the
generated executable on gdb, It says no debugging symbols found.

When I compiled the same assembly file using gcc(using the -g compile option),
the executable created contained the debug information.

When I looked into the the executables generated using the readelf -a command,
I found that the .debug_* info is absent from the clang compiled executable.

Attached the assembly file which is being used.
Quuxplusone commented 12 years ago

Attached thumb2-it.S (3999 bytes, text/plain): The assembly file used for generating the executable

Quuxplusone commented 12 years ago

This bug actually makes clang unusable under Windows, is there a chance it will addressed?

Quuxplusone commented 12 years ago 
The bug (In reply to comment #2)
> This bug actually makes clang unusable under Windows, is there a chance it
will
> addressed?
The bug is not connected with windows at all.
Quuxplusone commented 12 years ago 
Obviously you think/knows its not a Windows specific , but
the fact remains: its un-usable under Windows ;)