https://linen.dev logo
Join Discord
Powered by
# lime
  • p
    We're dealing with a segfault (or something like that) somewhere, which I don't think the hxcpp debugger can actually catch.
  • p
    That should be fine.
  • g
    had to set it manually apparently, gave an error about not finding an asset folder
  • g
    oh?
  • g
    theres a comment
  • g
    this is in
  • p
    A segfault, as suspected. Now, it should show a stack trace somewhere, that'll give more info.
  • g
    it seems to be a similar situation as it was here
  • g
    though i have no idea if it's still the vorbis stuff or not
  • a
    I still think it's a null reference 👼
  • g
    showing rendering stuff before that
  • g
    i'd been using paranoid if statements around the new file
  • g
    could my native libraries just be corrupted somehow or osmething?
  • p
    Maybe, although that seems a bit unlikely. Could you share the complete stack trace?
  • g
    sure. im not sure how to copy it as text here though
  • p
    A screenshot is fine too.
  • g
    wait hold on wrong one
  • g
    there
  • g
    could it somehow be a problem with the hxcpp debugger somehow?
  • g
    theres a crash that happens before my code related to music that i added recently even runs
  • g
    but it only happens when i run the build after building it through lime
  • g
    as vscode does automatically
  • g
    there it is
  • g
    it returns the same error though
  • g
    val_data line 264
  • g
    followed by something in lime.ndll and hten grpahics calls
  • r
    UncaughtErrorEvent
    is not able to catch issues in the underlying C++. it's meant for Haxe exceptions only (not necessarily all of them... just those related to OpenFL mostly).
  • g
    right
  • g
    so stuff that hxcpp debugger would catch anyway
  • g
    ok. wow
1...858687...138Latest