Page 1 of 1

Malformed packet when using gdb

Posted: Sat Nov 05, 2016 10:25 pm
by kolban
I have a situation where my ESP32 hosted app fails. I changed my make menuconfig to halt and launch the gdb stub. When the app fails, my goal is not to launch gdb and see what happened. I run the following command:

Code: Select all

xtensa-esp32-elf-gdb ./build/app-template.elf -b 115200 -ex 'target remote /dev/ttyUSB0'
This returns the following:

Code: Select all

GNU gdb (crosstool-NG 8d95cad) 7.10
Copyright (C) 2015 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 "--host=x86_64-build_pc-linux-gnu --target=xtensa-esp32-elf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://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 ./build/app-template.elf...done.
Remote debugging using /dev/ttyUSB0
Ignoring packet error, continuing...
Malformed packet(a) (missing colon): eout
Packet: 'T1feout'

(gdb) 
What I'm curious about are the last few lines which read:

Code: Select all

Ignoring packet error, continuing...
Malformed packet(a) (missing colon): eout
Packet: 'T1feout'
Is this indicative of an issue or problem?