LpcXpresso 7.11 GDB internal error

[lpcware]

Content originally posted in LPCWare by micronpn on Sat Jul 19 09:59:10 MST 2014
The only way to reover the error seems to be reboot or closing the user session.
This is the messages copied by the console:

The target endianness is set automatically (currently little endian)
/home/build/work/GCC-4-8-build/src/gdb/gdb/linespec.c:2445: internal-error: decode_line_full: Assertion `state->canonical_names.suffix != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) [answered Y; input not from terminal]

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
/home/build/work/GCC-4-8-build/src/gdb/gdb/linespec.c:2445: internal-error: decode_line_full: Assertion `state->canonical_names.suffix != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) [answered Y; input not from terminal]

[lpcware]

Content originally posted in LPCWare by micronpn on Mon Jul 21 05:50:53 MST 2014
Whe problem happened I had no breakpoints set. I already had device enumerated so to test data reception and send I didn't use breakpoints. It seems retalted to the presence of a device connected on the USB host port already during the flash programming at the beginning when I started the debug, seems a lot more frequent in that phase, I am quite able to reproduce it in this way. So I suppose that using my application, an EA AOAA board, a LpcLink-2 and LpcXpresso rel. 7.11 tring to start the debug so that LpcXpresso should also build the application you should be able to experience the same problem I have here.

Actually id I remember to detach the device USB cable before to start the debug session seems that hte problem doesn't happen anymore, at least doesn't happen from this morning when I found a relation to the connected cable so may be about 20-25 builds.

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Mon Jul 21 03:05:50 MST 2014
Did you follow the thread that I posted? The suggestion in there was to delete your breakpoints. I have not been able to verify if this works as I am unable to reproduce the problem...

[lpcware]

Content originally posted in LPCWare by micronpn on Mon Jul 21 02:14:22 MST 2014
I had the same problem this morning 3 times.

The 2nd time I tried to do everything possible step by step and LpcXpresso restarted after disconnecting the USB cable connecting the external device to the USB host port.

Because it wasn't the first thing I did, the 3rd time I tried only disconnecting the USB cable and LpcXpresso restarted.

I can't be totally sure but seems that the problem is related to that.

The board I am using is a EA LPC1769 AOAA board so eventually you can test on it with the sw I sent yesterday. The external device I connected is a Logitech Elite keyboard or a Sandisk USB memory key or a WiFiDipCortex (by SolderSplash).

This morning the WiFiDipCortex was connected.

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Mon Jul 21 00:33:16 MST 2014
Although we have been unable to reproduce this issue, you may find this thread (reporting the same GDB error), useful.

http://www.lpcware.com/content/forum/issues-lpcexpresso-70092

[lpcware]

Content originally posted in LPCWare by micronpn on Sun Jul 20 04:22:21 MST 2014
I already said in the previous post: LpcLink-2.

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Sun Jul 20 02:02:06 MST 2014
Which debug probe are you using?

[lpcware]

Content originally posted in LPCWare by micronpn on Sat Jul 19 14:38:02 MST 2014
1. No I am not linking with external libraries in object code.
2. It happens randomly without any clear reason.
3. I am using LpcXpresso 7.11
4. It happens more frequently with UsbKeyboardHost project but happens also with UsbMassStorageHost project..
5. I added a zip archive containing all my test workspace (UsbMassStorageNoWaitHost and UsbVcomHoat are working in progress so don't care about them).
6. I am using an Embedded Artists AOAA kit and a LpcLink2 as debugger probe.
7. The hardware used for the test it is a Logitech Elite keyboard.
8. The USB memory keys used to test are SanDisk and Verbatim models, also some unknown sponsored models are used.

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Sat Jul 19 10:47:55 MST 2014
Are you linking your application with a 3rd party library? Or a library created with another tool chain?

We have found that there are some tools from other vendors that produce bad debug tables in libraries. The way to resolve this is to remove the debug table from the library and to link with this new library.

To strip debug information from a library, run the following command

arm-none-eabi-objcopy -d liboriginal.lib libnew.lib

You can then find out if this fixes the issue by running the following command

arm-none-eabi-gdb application.axf --readnow

If none of this applies to your scenario, please post your application and exact details on how to reproduce the problem. Note that unless we have enough information to reproduce the problem here, then we cannot investigate the problem.