https://linen.dev logo
Join Discord
Powered by
# lime
  • g
    tryna find the cause
  • g
    i THINK i did but when i went back to msvc it kept happening
  • p
    And how would mingw help with debugging a silent crash? Just run your binary with a debugger. Visual Studio has one builtin, and VSCode has extensions.
  • g
    yes i mean the kind of silent crash vscode doesnt catch
  • g
    it just hard cuts to ECONRESET which i've learned meant "vscode has lost connection to your program"
  • p
    Huh, interesting. But I still don't see how mingw would help.
  • g
    it kind of did, a little, using mingw meant i could run it through GDB
  • p
    (Also, which debugger are you using. An actual C++ debugger, or the hxcpp one?)
  • a
    gdb lol
  • g
    usually i use uhh
  • g
    the hxcpp one i think?
  • g
    im not really sure what identifies what vscode uses when i tell it todebug
  • g
    probably hxcpp cause its doing a hxcpp debug server
  • p
    Right, when I say debugger I mean an actual debugger like the one built in to Visual Studio, not the hxcpp one.
  • p
    There's probably a segfault happening somewhere, and I don't think the hxcpp debugger can catch those.
  • g
    speaking of crashes the code im working off of had a crash handler implemented to it but im not even sure what kind of crashes these are meant for
  • g
    ive rarely used visual studio or whatever it was like, as a program was crashing
  • g
    but ive never like, used it beforehand
  • g
    how would i set a vs debugger up
  • p
    The easiest would probably be to use vscode + Just point the debug configuration at the executable and press launch. You can also use Visual Studio, but I'm not entirely sure how you'd debug a standalone binary with it (I usually use Linux, so I'm not that familiar with VS)
  • g
    oh vscode has that installed for me already
  • g
    so currently my debug configuration just says "lime"
  • g
    and i cannn
  • p
    C/C++: (Windows) Launch is the one you want
  • p
    You'll need to point it at the executable in 
    export/windows/bin
    (and set export/windows/bin as working directory)
  • g
    right
  • a
    that should be fine to use
  • g
    thats cwd, and it says "${fileDirname}
  • a
    iirc lime sets up the debug config on the selected display config
  • g
    theres a lot of context here . the most impotant thing is that theres an error hxcpp isnt catching
1...848586...138Latest