Open geek opened 8 years ago
@jclulow we could do that. I do think your suggestion will be easier to use, but I prefer to make it a separate step and the path explicit. Would you thoth upload node
and then associate it with an object?
Presumably this is for situations where the debugging information is not included in the core file itself, so the original executable is also needed to provide mdb
with a complete picture?
I think I would probably extend thoth upload
to optionally accept a binary as well as a core file, and to track it as a first class artefact alongside the core itself.
@jclulow that makes sense. I will let you make the call on if we should do that. It may complicate the code a bit to detect which of the files is the core, as well as checking if the binary is already uploaded (for potential reuse).
@jclulow this is now updated to upload the program that created the core and associate it with the core for loading into MDB.
Would it be better to provide a way to upload a binary for a particular thoth dump, and to have
thoth debug
then use it each time automatically?