Feature Request: Add backtrace information to RemoteException

[schlichtanders]

I am currently trying to figure out where this bug #65 comes from.

Unfortunately, Malt.jl misses to print stacktraces. Pluto has perfect support for stacktraces, but Malt misses them. It's a pity which will cause me at least a full working day of work...

Maybe you can copy the logic from Pluto.PlutoRunner.CapturedException?

[schlichtanders]

I found the location which needs to be changed:

Malt.jl/src/worker.jl

Line 80 in 34e6226

err, false

Probably it is easiest to directly transform it to a string like it is done in a similar place

Malt.jl/src/worker.jl

Lines 126 to 128 in 34e6226

	(false, sprint() do io
	Base.invokelatest(showerror, io, e, catch_backtrace())
	end)

Or altrnatively delete the sprint transformations early on and do it during construction of Malt.RemoteException (or even better as showerror implementation of Malt.RemoteException)

[Pangoraw]

Or altrnatively delete the sprint transformations early on and do it during construction of Malt.RemoteException (or even better as showerror implementation of Malt.RemoteException)

The exception needs to be deserializable on the "main" process which is why we convert to string.