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.

Sign up for GitHub

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

Jump to bottom

[LLDB][MIPS] TestInferiorAssert tests fail if section .gnu_debuglink is not available in libc.so.6 #26966

Closed
llvmbot opened this issue Feb 12, 2016 · 6 comments
Closed

[LLDB][MIPS] TestInferiorAssert tests fail if section .gnu_debuglink is not available in libc.so.6 #26966

llvmbot opened this issue Feb 12, 2016 · 6 comments
Labels
bugzilla Issues migrated from bugzilla lldb obsolete Issues with old (unsupported) versions of LLVM test-suite

Comments

@llvmbot
Copy link
Collaborator

llvmbot commented Feb 12, 2016

Bugzilla Link 26592
Version unspecified
OS Linux
Reporter LLVM Bugzilla Contributor

Extended Description

The loaded library (like libc.so) may not have its debug version available on the system (section .gnu_debuglink is not available). The debug version contains additional symbol information (such as __assert_perror_fail). Backtrace/function bound fails when symbol information is missing.
@llvmbot
Copy link
Collaborator Author

llvmbot commented Oct 18, 2018

I can confirm that the problem is still existent in r343771.

@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 10, 2021
@DavidSpickett
Copy link
Collaborator

We no longer support Linux MIPS debug.

https://lldb.llvm.org/#platform-support

@Endilll
Copy link
Contributor

Endilll commented Sep 8, 2023

@DavidSpickett Can you add obsolete label to issues you're closing for this reason?

@Endilll Endilll added test-suite obsolete Issues with old (unsupported) versions of LLVM labels Sep 8, 2023
@Endilll Endilll closed this as not planned Won't fix, can't repro, duplicate, stale Sep 8, 2023
@DavidSpickett
Copy link
Collaborator

Can you add obsolete label to issues you're closing for this reason?

...sure let me remember find the list of the others I just closed.

@DavidSpickett
Copy link
Collaborator

Ah I see you did them, thanks!

I'll use the labels as well in future.

@Endilll
Copy link
Contributor

Endilll commented Sep 8, 2023

Don't forget to close issues as not planned when it's appropriate as well!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bugzilla Issues migrated from bugzilla lldb obsolete Issues with old (unsupported) versions of LLVM test-suite
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@DavidSpickett @Endilll @llvmbot