gdb COM13: No such file or directory.

[preetam]

Hi Team,

I am using make monitor and there seems to be load prohibited error in my code, make monitor invokes gdb automatically but i don't see where it is pointing to in my code, I am using windows pc

Code: Select all

Entering gdb stub now.
$T0b#e6GNU gdb (crosstool-NG crosstool-ng-1.22.0-61-gab8375a) 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=i686-host_pc-mingw32 --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 C:/project/.../myproject.elf...done.
COM13: No such file or directory.
(gdb)

Does anybody know how to overcome this issue

[chegewara]

Its because you have esp32 connected on different com port or this port is used by other serial application like putty. In other words, gdb cant connect to esp32 on com13.

[preetam]

Hi ,

Thank you for the reply.
I am pretty sure that i am not using this port with other tools.
I am using make monitor and it is able to connect to com13 and display the flow.
However when a load prohibition takes place, the gdb stub is invoked as i have checked this in the menu config.
But the invoked gdb stub does not fetch com13

[chegewara]

From my experience, i am using putty to monitor program and see when and where it crash. Then i am running gdb in msys window with

Code: Select all

xtensa-esp32-elf-gdb ./build/app-template.elf -b 115200 -ex 'target remote COM3'

and can debug it.

[JimmyPedersen]

From my experience, i am using putty to monitor program and see when and where it crash. Then i am running gdb in msys window with

Code: Select all

xtensa-esp32-elf-gdb ./build/app-template.elf -b 115200 -ex 'target remote COM3'

and can debug it.

13!=3

In your comments you write COM13 but in your working example you use COM3.
Or are they different physical connections?

[WiFive]

13!=3

Not same author.

[ESP_Angus]

Hi Preetam,

That's quite strange, the make monitor gdb invocation works for me using the latest precompiled toolchain (same as the one you have) & current IDF on Windows 10.

The error seems to indicate COM13 has disappeared from the system some time between the initial monitor process starting and the invocation of gdb. When the monitor tool is about to automatically start gdb it closes the serial port, and then launches gdb with the same serial port name it was using. (Once gdb exits, the monitor tool will re-open the port.)

Some questions:

• If the crash is coupled with a power issue or something similar, is it possible COM13 has actually disappeared due to a brownout taking out the USB/serial interface?
• What ESP32 hardware are you using?
• Can you please post the full output from "make monitor", rather than just the last part?
• Is the Windows machine a VM or is there anything else unusual about the way the serial port is created?
• What path is your project at (ie what is the directory you run "make" in)?

[preetam]

Hi,

Currently after increasing the stack of the task, the Load Prohibition is not arising. I am sure that the issue will arise in the future as i may be passing a null to socket connect. I will post the full log once i come across the same.

Thanks and Regards,
Paul

[kolompos]

Try setting the assigned port number to less than 10. My problem was also a 'no such file or directory' but when i assigned COM port number 3 instead of 10 it worked.