If you only need to know how far you're getting before the crash you could
try directly embedding JS console.log() calls:
#include <emscripten/emscripten.h>
...
void bla() {
...
EM_ASM(console.log('I am here'));
...
}
But since this is an "Aw snap" error, not a Javascript exception, this
looks like a regression in Chrome's WASM implementation so I guess the best
you can hope for with debugging the WASM is what code construct causes the
crash...
I would definitely also write a Chrome ticket at https://crbug.com
Also Chrome has a crash log at chrome://crashes/ for uploaded crash
reports, and each crash gets a crash-id, this will be useful to include the
ticket. If you click on "Provide additional details" it will take you
automatically to the bug tracker and open a new ticket.
You may need to enable this crash reporting first though:
https://www.chromium.org/for-testers/bug-reporting-guidelines/reporting-crash-bug
Good luck!
-Floh.
On Thursday, 21 February 2019 03:34:14 UTC+1, [email protected] wrote:
>
> Wait, nevermind, that was just my printf debugging not getting flushed
> before the crash.
>
> OK, so I have this complicated function (a decompression function) that
> runs on all the other browsers (and ran in older Chrome versions), but now
> just crashes. What's the best way to debug this? Printf doesn't seem
> reliable, since it dies before output (I guess I could try a fflush(stdout
> );).
>
> Is there any logging I can compile with or anything?
>
>
> On Wednesday, February 20, 2019 at 6:17:54 PM UTC-8,
> [email protected] wrote:
>>
>> First function in main(), dies with a "Aw, Snap! Something went wrong
>> while displaying this webpage." error.
>>
>> Runs fine in Firefox, Edge, and Safari - what's the best way to track
>> this down?
>>
>
--
You received this message because you are subscribed to the Google Groups
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
