Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

X86/ELF Dwarf Support Is Lacking #1350

Closed
llvmbot opened this issue Nov 1, 2006 · 12 comments
Closed

X86/ELF Dwarf Support Is Lacking #1350

llvmbot opened this issue Nov 1, 2006 · 12 comments
Labels
bugzilla Issues migrated from bugzilla llvm:codegen wrong-debug

Comments

@llvmbot
Copy link
Collaborator

llvmbot commented Nov 1, 2006

Bugzilla Link 978
Resolution FIXED
Resolved on Feb 22, 2010 12:50
Version trunk
OS Linux
Reporter LLVM Bugzilla Contributor
CC @asl

Extended Description

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.

@lattner
Copy link
Collaborator

lattner commented Nov 1, 2006

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

@llvmbot
Copy link
Collaborator Author

llvmbot commented Nov 1, 2006

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.

@llvmbot
Copy link
Collaborator Author

llvmbot commented Nov 1, 2006

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.

@lattner
Copy link
Collaborator

lattner commented Nov 1, 2006

ok, excellent.

@asl
Copy link
Collaborator

asl commented Nov 1, 2006

I think the same issue applies to mingw debugging information too.

@llvmbot
Copy link
Collaborator Author

llvmbot commented Nov 3, 2006

Devang? How was this fixed? I still get the problem on Linux.

@llvmbot
Copy link
Collaborator Author

llvmbot commented Nov 3, 2006

I accidently resolved this bug. Reopening.

@lattner
Copy link
Collaborator

lattner commented Jan 14, 2007

is this still an issue?

@llvmbot
Copy link
Collaborator Author

llvmbot commented Mar 7, 2007

Yes, it is still an issue.

@asl
Copy link
Collaborator

asl commented Mar 7, 2007

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....

@asl
Copy link
Collaborator

asl commented Mar 7, 2007

Fixed .s

@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 3, 2021
trevor-m pushed a commit to trevor-m/llvm-project that referenced this issue Apr 20, 2023
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugzilla Issues migrated from bugzilla llvm:codegen wrong-debug
Projects
None yet
Development

No branches or pull requests

3 participants