Timeline for GDB remote: step/next "Cannot find bounds of current function"
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 21 at 18:56 | comment | added | John Lasseter |
@Kingsley - That's probably true. I took me almost a full day to figure out the basic mechanics of this Docker+QEMU+GDB combination, as I had to cobble it together from about a dozen sources. I meant to add on to my comment above that the full command to get everything to load correctly is to still include the target file as an argument, along with the -ex file <etc.> command. Any idea why that is? Why is the file argument even necessary?
|
|
| Jan 21 at 0:17 | comment | added | Kingsley | This is a good question for others having the same issue though. | |
| Jan 20 at 19:03 | comment | added | John Lasseter |
Bah. Sometimes you just need to write up something like that to solve it yourself. For one, I had the wrong sysroot value, which was evident from that initial "dynamic linker" warning. Also, I needed to use the file command explicitly. I'm not sure why, still. tl;dr version: I should have invoked GDB with bash gdb -ex 'target remote localhost:1234' -ex 'set sysroot /opt/riscv/sysroot' -ex 'file /root/buggy_sel_sort'
|
|
| S Jan 20 at 18:34 | review | First questions | |||
| Feb 3 at 18:35 | |||||
| S Jan 20 at 18:34 | history | asked | John Lasseter | CC BY-SA 4.0 |