[lldb-dev] [Bug 16582] New: Only one frame on call stack when running 32 bit app under 64 bit LLDB
bugzilla-daemon at llvm.org
bugzilla-daemon at llvm.org
Tue Jul 9 17:37:17 PDT 2013
http://llvm.org/bugs/show_bug.cgi?id=16582
Bug ID: 16582
Summary: Only one frame on call stack when running 32 bit app
under 64 bit LLDB
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: All Bugs
Assignee: lldb-dev at cs.uiuc.edu
Reporter: sorrels.m at gmail.com
Classification: Unclassified
Created attachment 10847
--> http://llvm.org/bugs/attachment.cgi?id=10847&action=edit
Small test app to demo this bug
When using Linux 64 bit lldb to debug a 32 bit application, the call stack only
shows one frame. This causes a number of the tests in the test suite to fail,
include TestFrames.py (a good example). Attached is a simple test app and a
debug session. When the break occurs in function f2, there should be four
functions on the call stack (main, f0, f1 and f2), but a bt only lists frame #0
(lldb) b f2
Breakpoint 1: where = 32bittest`f2 + 18 at main.c:5, address = 0x08048402
(lldb) run
Process 4127 launched: '/home/matthews/bin/32bittest' (i386)
In f0, calling f1
In f1, calling f2
Process 4127 stopped
* thread #1: tid = 0x101f, 0x08048402 32bittest`f2(val=65) + 18 at main.c:5,
stop reason = breakpoint 1.1
frame #0: 0x08048402 32bittest`f2(val=65) + 18 at main.c:5
2
3 int f2(int val)
4 {
-> 5 printf("In f2, returning\n");
6 }
7
8 int f1(int val)
bt
* thread #1: tid = 0x101f, 0x08048402 32bittest`f2(val=65) + 18 at main.c:5,
stop reason = breakpoint 1.1
frame #0: 0x08048402 32bittest`f2(val=65) + 18 at main.c:5
(lldb)
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20130710/882882ef/attachment.html>
More information about the lldb-dev
mailing list