Interactive Mode

[discostu105]

Motivation:
In order to seriously debug a crash dump, which does not reveal it's real reason from a SuperDump report, one must still download the crash dump, start a debugging tool (e.g. WinDbg, gdb) and investgate further. For Windows users, who need to debug Linux crash dumps (and vice versa), this is painful. Also, some setup stuff always needs to be prepared (e.g. correct symbol path). What if SuperDump offered a web-based console which allows for interactive debugging?

Goal:
On a crash report page, offer a button for "Interactive Mode". It would show a console window in the browser. In the background, SuperDumpService would actually start a process (e.g. cdb.exe, gdb), load the given crash dump (maybe do other preparation steps) and redirect input/output to the console window.

It would make sense to start the process in a docker-container to protect the outer environment.

[discostu105]

https://github.com/projectkudu/kudu actually uses a web-based console window, also starting a cmd.exe process server-side and just redirect input/output to the browser via SignalR (see https://github.com/projectkudu/kudu/blob/b530c444f6f9c09d93fa569b2e490ad90ed6fa8e/Kudu.Services/Commands/PersistentCommandController.cs).

Unfortunately, SignalR is not available for .NET Core yet, so it'll be hard to port.

I'm wondering if there are any libraries out there which already do stuff like that.

[discostu105]

Just prototyped this: https://www.youtube.com/watch?v=Hx4LXDFQWR0

So, it's feasible :). Very dirty prototype though.

[discostu105]

done #28