Amaan Qureshi
Amaan Qureshi
enter `c` for continue and when it crashes, `bt` for the backtrace
hmm yeah some segfaults/crashes can kill/mess up a backtrace, try a few more times maybe? otherwise it's really hard to pinpoint - what filetype is it btw?
you could also try stopping on exceptions or certain signals like sigsegv, might help `catch throw` and `process handle SIGSEGV --stop true --pass true --notify true` respectively in lldb
> [@amaanq](https://github.com/amaanq) > > you could also try stopping on exceptions or certain signals like sigsegv, might help > > > > `catch throw` and `process handle SIGSEGV --stop true...
> Got yet another exit status `141`: > > are you able to get a backtrace here..?
I can confirm that the fix works for me as well, finally :slightly_smiling_face:
Negations in tests are a thing now, I hope that fits your use case.
@ahelwer can you rebase to fix the conflicts?
Yeah I believe @ahlinc did,
Hmm, I can't reproduce this anymore w/ the lua example (I get a01), it might be fixed