Failed to execute MI command: -target-select remote localhost:3333

Bug #1688473 reported by zaleyu on 2017-05-05
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNU ARM Embedded Toolchain
Undecided
Unassigned

Bug Description

Dear sir:
We encountered a very rare problem that arm-none-eabil-gdb failed to execute the command of target remote localhost:3333 when trying to connect to the gdb server (OpenOCD). When failed, the gdb command line showed an error message: localhost:3333: The system tried to join a drive to a directory on a joined drive. We have tried to turn off the firewall, but the result remained. Could you provide any solution? Or is there any log file we can refer to? Thank you.

The details were:
1. GNU gdb version: 6-2017-q1-update 7.12.1.20170215-git
2. I was using the binary package which was downloaded from https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads
3. Host machine was Windows 7 with x64 platform.
4. GDB configuration: --host=i686-w64-mingw32 --target=arm-none-eabi
5. symptom: failed to execute the command of target remote localhost:3333
6. Error message: localhost:3333: The system tried to join a drive to a directory on a joined drive.

Tejas Belagod (belagod-tejas) wrote :

Hi,

Thanks for the bug report. We will try and reproduce this on our side with our harddware. Is this something new you're seeing with 6-2017-q1-update? Have you tried with older versions?

Also, what setup (hardware, interface etc?) are you trying to connect to using OpenOCD? It might be specific to your setup, so reproducing it on our side might be non-trivial.

Thanks,
Tejas.

zaleyu (zaleyu) wrote :

Dear sir:
Honestly speaking, this issue only happened on one PC used by my colleague.
On my computer, everything was fine. Therefore, I think it would be hard to reproduce the issue.
On his computer, we have tried to use the older versions (6.2 2016q4). The result remained.
However, we can use the Windows command line to successfully make the command of telnet localhost 4444 and connect to the OpenOCD. From my perspective, the setup of OpenOCD should have no problem.

Is there any log file so that we can dig more? Or do you have any advice that we can follow?

Thank you.

Sincerely,
Zale Yu

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers