AnsweredAssumed Answered

Error No source available for "(gdb[2].proc[42000].threadGroup[i1],gdb[2].proc[42000].OSthread[1]).thread[1].frame[0]"  during debugging start

Question asked by Pavlo Kostrytsia on Apr 7, 2020
Latest reply on Apr 17, 2020 by Omar Anguiano

I am using MCUXpresso IDE v11.1.1 [Build 3241] [2020-03-02] on Windows 10 computer with LPCXpresso LPC-Link 2 as a debug tool and NXP Kinetis K8x MCU as a target. When I start the debug session, after uploading, I get the following error (you can also check the screenshot in attachment):

No source available for "(gdb[2].proc[42000].threadGroup[i1],gdb[2].proc[42000].OSthread[1]).thread[1].frame[0]" 

With pressing buttons Suspend and Resume I get the following error:

Break at address "0x1c00520e" with no debug information available, or outside of program code.

While Console shows the message

[MCUXpresso Semihosting Telnet console for 'EOS_K8x LinkServer Debug Build' started on port 51504 @]

Debugger Console shows the following:

C:\mcuxpresso\MCUXpressoIDE_11.1.1_3241\ide\plugins\ ools in rm-none-eabi-gdb.exe: warning: Couldn't determine a path for the index cache directory.
GNU gdb (GNU Tools for Arm Embedded Processors 8-2019-q3-update)
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <>
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-w64-mingw32 --target=arm-none-eabi".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
Find the GDB manual and other documentation resources online at:

For help, type "help".
Type "apropos word" to search for commands related to "word".

Program stopped.
0x1c0001ec in ?? ()

Program received signal SIGINT, Interrupt.
0x1c00520e in ?? ()


I have experienced similar issues with MCUXpresso IDE v10.3.1. However, repetitive pressing of the buttons Suspend, Resume, and Restart helped to proceed with debugging in most of the cases.


How to resolve this problem?