|
Back
Midas
Rome
Roody
Rootana
|
Midas DAQ System |
Not logged in |
|
|
08 Jul 2019, Vinzenz Bildstein, Bug Report, Frontend killed at stop of run
|
08 Jul 2019, Konstantin Olchanski, Bug Report, Frontend killed at stop of run
|
08 Jul 2019, Vinzenz Bildstein, Bug Report, Frontend killed at stop of run
|
08 Jul 2019, Konstantin Olchanski, Bug Report, Frontend killed at stop of run
|
08 Jul 2019, Vinzenz Bildstein, Bug Report, Frontend killed at stop of run
|
08 Jul 2019, Konstantin Olchanski, Bug Report, Frontend killed at stop of run
|
08 Jul 2019, Vinzenz Bildstein, Bug Report, Frontend killed at stop of run
|
10 Jul 2019, Vinzenz Bildstein, Bug Report, Frontend killed at stop of run
|
10 Jul 2019, Konstantin Olchanski, Bug Report, Frontend killed at stop of run
|
11 Jul 2019, Vinzenz Bildstein, Bug Report, Frontend killed at stop of run
|
11 Jul 2019, Konstantin Olchanski, Bug Report, Frontend killed at stop of run
|
16 Jul 2019, Konstantin Olchanski, Bug Report, a3818 and signals, Frontend killed at stop of run
|
16 Jul 2019, Konstantin Olchanski, Bug Report, a3818 and signals, Frontend killed at stop of run
|
|
Message ID: 1601
Entry time: 08 Jul 2019
In reply to: 1598
Reply to this: 1602
|
Author: |
Vinzenz Bildstein |
Topic: |
Bug Report |
Subject: |
Frontend killed at stop of run |
|
|
> run the frontend inside gdb and post the stack trace after the crash?
>
> if there is no crash (the program is stopped by exit()), you may need
> to set a breakpoint in exit() or _exit() (not sure what it's latest name is)
> then with luck your stack trace will show who/what called it from where.
>
If I remember correctly from the last time I tried that, it doesn't use the exit
function but gdb just reports that the program was terminated and no longer exists. I
can't set a breakpoint on SIGKILL as the point of SIGKILL is to kill the program and
gdb can't set a break at that point afaik. |