>I think a SIGSEGV is not the best way to fail.
Zero arguments here :) I'm just checking if it was the same issue or different seg fault. I'll add a bug watch so that this will be automatically updated if something happens in the Debian report.
>I think a SIGSEGV is not the best way to fail.
Zero arguments here :) I'm just checking if it was the same issue or different seg fault. I'll add a bug watch so that this will be automatically updated if something happens in the Debian report.