<html><head></head><body><div class="yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div id="ydp4ec87aafyahoo_quoted_1168241402" class="ydp4ec87aafyahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
Am Freitag, 22. Februar 2019, 07:43:50 MEZ hat Steve Lhomme <robux4@ycbcr.xyz> Folgendes geschrieben:
</div>
<div><br></div>
<div><div dir="ltr"> <span> <span>> Not only gdb+qt is a bad combination (you either choose to get 20 breaks<br>> at each run or break on legit asserts) but it's not the worst part.<br><br>From what I can tell, there's a difference between msvcrt.dll and<br>ucrtbase.dll, it's not really depending on the debugger (try the attached<br>test program in both debuggers to compare).<br><br>Also, if I have to debug an assertion failure in gdb, I set a<br>breakpoint on ExitProcess, that always works for me.<br><br><br>> VLC has hundreds of DLLs and loads tens of them just to play a file<br>> (that's when you have plugins cache working). For every DLL loaded gdb<br>> tries to load the symbol. In worst cases (if you happen to set more than<br>> 2 breakpoints) it can take 1s per DLL on my super fast machine (and all<br>> other machines I've used in the past years). Making debugging any line<br>> change a nightmare. Let alone the code that times out because the<br>> debugger didn't finish loading some other parts.<br><br>> MSVC has none of these issues, it's very fast to load and you can put<br>> keep 100 breakpoints and works just as fast.<br><br>I agree that gdb is very slow with many DLLs.</span></span><br></div></div>
</div>
</div></div></body></html>