LLDBFrontend crash

and the related setting are as follows.

Hi! 

If you can reproduce it stably, please create the ~/.lldbinit file, add log enable -f C:\Windows\Temp\lldb-log.txt lldb all to it (you can use any other folder instead of temp), save changes, and reproduce the issue in CLion after that. Please send the resulted log (C:\Windows\Temp\lldb-log.txt) to clion-support at jetbrains.com, so we can take a look.

where do I to create the file lldbinit , My system is win7 , I don't install lldb by myself . I use the clion bundled

>where do I to create the file lldbinit

In the user home directory. Note that it should be ".lldbinit".

Also could you please empty the "Make" field, apply the changes and try to debug the project? Does it work in this case?

I empty the "Make" field, still it crashed again. 

the lldb-log.txt can be download from here. https://pan.baidu.com/s/1myjiY0ko5ux6CaRwqDUeLw&shfl=sharepset 

click the the logo as the image shows.

It seems it asks me to login.

Please upload the log to https://uploads.services.jetbrains.com/ and tell me the file name. Or just send it in email to clion-support at jetbrains.com.

I have upload the file  lldb-log20191020.txt to your upload location , Hope it helps . 

Unfortunately, the log didn't help to determine the reason.

1. Please close your project (File | Close Project), on the Welcome screen choose New Project, choose C++ Executable, click Create. Does the debug process work correctly for this project?

2. Does the debug process work correctly for your project in case of MinGW?

for new project , it work fine.

for my project in case of MinGw , it work fine

I just roll back to 2019.2.4  , everything works fine .  anything else can I provide with ? 

Please use 2019.2.4 for now and wait for the next CLion 2019.3 EAP build expected this week, it should include a related fix which might help in your case.

Ok ， I found another problem , on 2019.2.4 , it take a long time to load debug info . I think I should roll back to 2019.2.3

if I copy the relative dll  file to the exe path , and the ms debugger load the debugger info is very fast . 

It seems the problem has been fixed in the latest version . Well done . 

Thanks for letting us know!