https://bugzilla.redhat.com/show_bug.cgi?id=1859627
Jaroslav Kysela <jkysela(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jkysela(a)redhat.com
Flags| |needinfo?(austin880625@gmai
| |l.com)
--- Comment #23 from Jaroslav Kysela <jkysela(a)redhat.com> ---
Austin - a quick question, what does not work for you in the standard gdb
package? I'm just trying to debug the Raspberry Pi Pico (arm-none-eabi
compiler) and it seems working:
$ gdb -ex "target extended-remote localhost:3333" blink.elf
GNU gdb (GDB) Fedora 10.1-4.fc33
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <
http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<
https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<
http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from blink.elf...
Remote debugging using localhost:3333
warning: Remote gdbserver does not support determining executable
automatically.
RHEL <=6.8 and <=7.2 versions of gdbserver do not support such automatic
executable detection.
The following versions of gdbserver support it:
- Upstream version of gdbserver (unsupported) 7.10 or later
- Red Hat Developer Toolset (DTS) version of gdbserver from DTS 4.0 or later
(only on x86_64)
- RHEL-7.3 versions of gdbserver (on any architecture)
warning: multi-threaded target stopped without sending a thread-id, using
first non-exited thread
to_us_since_boot (t=...)
at /opt/pico-sdk/src/common/pico_base/include/pico/types.h:46
46 return t._private_us_since_boot;
(gdb) bt
#0 to_us_since_boot (t=...)
at /opt/pico-sdk/src/common/pico_base/include/pico/types.h:46
#1 time_reached (t=...)
at
/opt/pico-sdk/src/rp2_common/hardware_timer/include/hardware/timer.h:108
#2 sleep_until (t=...) at /opt/pico-sdk/src/common/pico_time/time.c:343
#3 0x10000d94 in sleep_us (us=<optimized out>)
at /opt/pico-sdk/src/common/pico_time/include/pico/time.h:102
#4 0x10000dce in sleep_ms (ms=ms@entry=250)
at /opt/pico-sdk/src/common/pico_time/time.c:367
#5 0x10000386 in main ()
at /home/perex/mysrc/rpi/pico/pico-examples/blink/blink.c:20
(gdb) break sleep_ms
Breakpoint 1 at 0x10000dbc: file /opt/pico-sdk/src/common/pico_time/time.c,
line 366.
Note: automatically using hardware breakpoints for read-only addresses.
(gdb) c
Continuing.
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
Thread 1 hit Breakpoint 1, sleep_ms (ms=ms@entry=250)
at /opt/pico-sdk/src/common/pico_time/time.c:366
366 void sleep_ms(uint32_t ms) {
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component