aha!... using "stdout" instead of "stderr" always gets rid of the stack
trace! (I can live with that..) now the only remaining question is how to
get EMSCRIPTEN to use my replaced (see above) console.log rather than the
original one...
juergen...@gmail.com schrieb am Freitag, 11. August 2023 um 14:29:49 UTC+2:
> thanks for the tip. that is indeed an improvement for the C++ case -
> unfortunately it doesn't help for my current C project. Also I'd like to
> completely get rid of the useless "source file" info (since it is a
> nuisance having to edit that out first when using the logs), something that
> I'd handle in the plain JavaScript context using something like this:
>
> function disableLogSourceDisplay() {
> var origLog = console.log;
>
> console.log = function (s1) {
> setTimeout(origLog.bind(console, s1)); // "lose" the original context
> };
> }
> disableLogSourceDisplay();
>
>
>
--
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 emscripten-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/emscripten-discuss/d4cc097c-ccdd-4001-a715-e7c174b2c4b0n%40googlegroups.com.
