LLVM Bugzilla is read-only and represents the historical archive of all LLVM issues filled before November 26, 2021. Use github to submit LLVM bugs

Bug 978 - X86/ELF Dwarf Support Is Lacking
Summary: X86/ELF Dwarf Support Is Lacking
Status: RESOLVED FIXED
Alias: None
Product: libraries
Classification: Unclassified
Component: Common Code Generator Code (show other bugs)
Version: trunk
Hardware: PC Linux
: P normal
Assignee: Unassigned LLVM Bugs
URL:
Keywords: wrong-debug
Depends on:
Blocks:
 
Reported: 2006-10-31 17:44 PST by Reid Spencer
Modified: 2010-02-22 12:50 PST (History)
3 users (show)

See Also:
Fixed By Commit(s):

Attachments
Fixed .s (7.51 KB, text/plain)
2007-03-06 17:45 PST, Anton Korobeynikov 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Reid Spencer 2006-10-31 17:44:03 PST 
The X86/ELF Dwarf support appears to be lacking some information that the
debugger needs. Although it is possible to set breakpoints, trace through the
program, and otherwise debug things, GDB will quite frequently print messages of
the form: 
During symbol reading, Incomplete CFI data; unspecified register eax at 0x08867e2d.
During symbol reading, Incomplete CFI data; unspecified register ecx at 0x08867e2d.
During symbol reading, Incomplete CFI data; unspecified register edx at 0x08867e2d.
During symbol reading, Incomplete CFI data; unspecified register ebx at 0x08867e2d.
During symbol reading, Incomplete CFI data; unspecified register esi at 0x08867e2d.
During symbol reading, Incomplete CFI data; unspecified register edi at 0x08867e2d.

These always occur with the "where" command and often occur when inspecting
variables or using the "next" command.

Possibly there is some frame information that is missing for X86/ELF.
Comment 1 Chris Lattner 2006-10-31 18:45:53 PST 
If debug info doesn't work right on X86/ELF, does it make sense to disable it until after the 1.9 release?  
Either we want to say it works or it doesn't.  We don't want a half-way state.

-Chris
Comment 2 Jim Laskey 2006-10-31 19:34:29 PST 
Reid implied that this was somewhat an esthetic issue (getting warnings from gdb), so I can go either way.  
However, to make a decision I would say, disable - they don't have it now - wait till it is less messy.
Comment 3 Reid Spencer 2006-10-31 20:40:20 PST 
Debugging works fine. As Jim said, its just a matter of making GDB shut up about
stuff it thinks it needs. You can do all the basic things: get stack trace, list
code (although paths are missing), inspect variables, set breakpoints, etc. It
all works, you just get lots of these warning messages. Implementing the
required info will probably make some esoteric functionality work better but I
haven't discovered what yet.

The X86/ELF debug stuff is fine for 1.9.
Comment 4 Chris Lattner 2006-10-31 21:29:43 PST 
ok, excellent.
Comment 5 Anton Korobeynikov 2006-10-31 23:42:23 PST 
I think the same issue applies to mingw debugging information too.
Comment 6 Reid Spencer 2006-11-03 11:52:03 PST 
Devang? How was this fixed? I still get the problem on Linux.
Comment 7 Devang Patel 2006-11-03 12:57:08 PST 
I accidently resolved this bug. Reopening.
Comment 8 Chris Lattner 2007-01-14 13:01:57 PST 
is this still an issue?
Comment 9 Reid Spencer 2007-03-06 17:37:44 PST 
Yes, it is still an issue.
Comment 10 Anton Korobeynikov 2007-03-06 17:45:21 PST 
Well. It seems, I've found the reason. Testing...

I've attached (fixed) SingleSource/UnitTests/2002-12-13-MishaTest.s

Could please anybody check, whether it's ok or not....
Comment 11 Anton Korobeynikov 2007-03-06 17:45:44 PST 
Created attachment 698 [details]
Fixed .s