We need a better way to handle node.js + pthreads errors

[VirtualTim]

With the changes made in #9863 errors in a node.js pthread are reported like pthread sent an error! undefined:undefined: Module is not a function.
This could be more helpful, it would be good to get a line number and file like we do in the web case. At a minimum undefined:undefined should go.

My suggestion would be to replace

emscripten/src/library_pthread.js

Line 441 in 408a6e9

worker.onerror(data);

with err('pthread sent an error!\n' + data.stack);. This will print out something like:

pthread sent an error!
TypeError: Module is not a function
    at onmessage (/path/module.worker.js:93:16)
    [stacktrace continues]

This is slightly more helpful. However I'm not familiar enough with node to know if there's something better.
Anyone have any better ideas?

[kripken]

cc @addaleax

[addaleax]

This is slightly more helpful. However I'm not familiar enough with node to know if there's something better.

This is what I would do too 👍 If you do want an alternative, it would be require('util').inspect(data), which generally aims to provide the most debugging-friendly representation of an object (it’s what Node uses for console.log()).

[stale]

This issue has been automatically marked as stale because there has been no activity in the past year. It will be closed automatically if no further activity occurs in the next 30 days. Feel free to re-open at any time if this issue is still relevant.

[sbc100]

This is still an issue. I just ran into what I think is the same thing in #12885. I think #11345 boils down to basically the same thing so we should probably merge them.

Is this really node only issue? Its seems to happen on the web as well?

[stale]

This issue has been automatically marked as stale because there has been no activity in the past year. It will be closed automatically if no further activity occurs in the next 30 days. Feel free to re-open at any time if this issue is still relevant.