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

Jump to bottom

Function stubs on the PLT show as __lldb_unnamed_symbol #52702

Closed
HFDan opened this issue Dec 14, 2021 · 4 comments
Closed

Function stubs on the PLT show as __lldb_unnamed_symbol #52702

HFDan opened this issue Dec 14, 2021 · 4 comments
Labels
lldb

Comments

@HFDan
Copy link

HFDan commented Dec 14, 2021

Whenever i use LLDB to debug my application, and i disassemble a function, calls to libc functions look like this:

call 0x1030 ; stub for __lldb_unnamed_symbol67

When i use GDB, calls to libc functions look like this:

call 0x1030 <puts@plt>

Why does LLDB not resolve symbol names for plt function stubs?
@poyaoc97
Copy link
Member

Potential fix: https://reviews.llvm.org/D116217

@poyaoc97
Copy link
Member

Closed by 633b002.

@Endilll
Copy link
Contributor

Endilll commented Sep 16, 2023

Commit: 633b002

@Endilll Endilll added lldb and removed new issue labels Sep 16, 2023
@llvmbot
Copy link
Collaborator

llvmbot commented Sep 16, 2023

@llvm/issue-subscribers-lldb

Whenever i use LLDB to debug my application, and i disassemble a function, calls to libc functions look like this:

call 0x1030 ; stub for __lldb_unnamed_symbol67

When i use GDB, calls to libc functions look like this:

call 0x1030 &lt;puts@<!-- -->plt&gt;

Why does LLDB not resolve symbol names for plt function stubs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lldb
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Endilll @poyaoc97 @HFDan @llvmbot