LLDBFrontend crash

Answered

clion info:

CLion 2019.3 EAP
Build #CL-193.4386.19, built on October 10, 2019
CLion EAP User
Expiration date: November 9, 2019
Runtime version: 11.0.4+10-b517.1 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 7 6.1
GC: ParNew, ConcurrentMarkSweep
Memory: 7987M
Cores: 16
Registry: run.processes.with.pty=TRUE, debugger.valueTooltipAutoShowOnSelection=true, cidr.debugger.gdb.workaround.windows.forceExternalConsole=true
Non-Bundled Plugins: GrepConsole

operation system : win7 x64 

compiler: visual studio 2017 debugger.

 

when I click the debug button on the clion , it show that LLDBFrontend crash.

 

 

19 comments
Comment actions Permalink

and the related setting are as follows.

0
Comment actions Permalink

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.

0
Comment actions Permalink

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

0
Comment actions Permalink

>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?

0
Comment actions Permalink

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

0
Comment actions Permalink

click the the logo as the image shows.

0
Comment actions Permalink

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.

0
Comment actions Permalink

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

0
Comment actions Permalink

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?

0
Comment actions Permalink

for new project , it work fine.

0
Comment actions Permalink

for my project in case of MinGw , it work fine

0
Comment actions Permalink

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

0
Comment actions Permalink

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.

0
Comment actions Permalink

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

0
Comment actions Permalink

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

0
Comment actions Permalink

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

0
Comment actions Permalink

Thanks for letting us know!

0

Please sign in to leave a comment.