Core file workflow

Core file workflow

[Phil Muldoon]

Discussed at the UI meeting.

Multiple entry points

- GNOME association with core files? Double click a core file and it 
opens up Frysk.
- File menu entry within Frysk. Open up a core file. Specify an 
executable, or just find the executable on disk? How to know if core 
file is from a  third-party?
- Command line option, IE frysk core.1234.

When opened in Frysk the source window view will be shown, bypassing 
monitor, session manager views. The stack-trace will represent where the 
main-thread was when the core file snapshot occurred. How to show the 
fault that caused the core file? The source view will be at the fault or 
snapshot point.

Questions outstanding redux:

When loading the core file into Frysk, where to find debug info?
Automatic executable discovery by default? (IE this core file needs 
/bin/bash)
How to show the fault that caused the core file (sigsegv, sigabrt etc)?
Multiple source viewer modes. You cannot step a core file. How to let 
the source window know what buttons to make sensitive?

Regards

Phil

Re: Core file workflow

[Phil Muldoon]

If there are no objections to how I remembered/wrote this up, I'll put 
it in the work-flow section of the website

Regards

Phil

Phil Muldoon wrote:
> Discussed at the UI meeting.
>
> Multiple entry points
>
> - GNOME association with core files? Double click a core file and it 
> opens up Frysk.
> - File menu entry within Frysk. Open up a core file. Specify an 
> executable, or just find the executable on disk? How to know if core 
> file is from a  third-party?
> - Command line option, IE frysk core.1234.
>
> When opened in Frysk the source window view will be shown, bypassing 
> monitor, session manager views. The stack-trace will represent where 
> the main-thread was when the core file snapshot occurred. How to show 
> the fault that caused the core file? The source view will be at the 
> fault or snapshot point.
>
> Questions outstanding redux:
>
> When loading the core file into Frysk, where to find debug info?
> Automatic executable discovery by default? (IE this core file needs 
> /bin/bash)
> How to show the fault that caused the core file (sigsegv, sigabrt etc)?
> Multiple source viewer modes. You cannot step a core file. How to let 
> the source window know what buttons to make sensitive?
>
> Regards
>
> Phil