PS: the above globally changes the console's behavior and has the side
effect that log calls made from unrelated JavaScript code will also no
longer show the "source file". The clean way is probably to define the
Module's "print" function by passing a respective object into the Module
Thanks for the tip. The behavior actually seems to depend on
std::cerr/stderr.. when stdout is used instead then the stacktrace is gone
(i.e. works also in C).
To then also get rid of the annoying "source file" info console.log has to
be replaced before the EMSCRIPTEN Module is instanciated,
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
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
>
> I sometimes just want to print trace output from the C/C++ side and I do not
> care about the stack trace info in that scenario. I already do know exactly
> where the messages come from and the stack unnecessarily bloats the output by
> 1-2 orders of magnitude - sometimes slowing the
