Bug 17026 - Cannot backtrace on executable generated by TI C6x compiler
Summary: Cannot backtrace on executable generated by TI C6x compiler
Status: NEW
Alias: None
Product: gdb
Classification: Unclassified
Component: backtrace (show other bugs)
Version: 7.7
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
: 17025 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-06-04 22:47 UTC by Ulises Brindis
Modified: 2014-06-05 08:11 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments
Test executable (496.56 KB, application/x-executable)
2014-06-04 22:50 UTC, Ulises Brindis
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ulises Brindis 2014-06-04 22:47:31 UTC
GDB cannot handle backtracing on executables generated by the TI C6x compiler. When running the bt command this is the frame information that is shown 

Program received signal SIGTRAP, Trace/breakpoint trap.
0x008105e6 in $C$L4 () at ../main.c:54
54      ../main.c: No such file or directory.
(gdb) bt
#0  0x008105e6 in $C$L4 () at ../main.c:54
PC not saved

If the command "info frame" is run, sometimes this is the output - 
(gdb) info frame
Stack level 0, frame at 0x81b4b8:
 PC = 0x8105e6 in myTask (../main.c:54); saved PC = <not saved>
 called by frame at
frame.c:472: internal-error: get_frame_id: Assertion `fi->this_id.p' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)

I have included a test executable.
Comment 1 Ulises Brindis 2014-06-04 22:49:37 UTC
This was found by compiling GDB for --host=arm-linux-gnueabi --target=tic6x-*-elf
Comment 2 Ulises Brindis 2014-06-04 22:50:05 UTC
Created attachment 7629 [details]
Test executable
Comment 3 Gary Benson 2014-06-05 08:11:14 UTC
*** Bug 17025 has been marked as a duplicate of this bug. ***