|
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: 1598
Entry time: 08 Jul 2019
In reply to: 1597
Reply to this: 1601
|
Author: |
Konstantin Olchanski |
Topic: |
Bug Report |
Subject: |
Frontend killed at stop of run |
|
|
> After a long overnight run to check that the frontend runs smoothly for a longer
> time, I stopped the run and the frontend was killed by midas.
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 it is hard to start the frontend inside gdb, you can start it normally,
and attach gdb later, using a "gdb frontend.exe pid" command.
K.O.
> I am not sure why
> this happened, as the end_of_run function returned successfully (at least the
> print statement right before "return SUCCESS;" appeared right away). So
> something else must have timed-out and caused it to be killed, I guess?
>
> Any suggestions on where to look to find out what causes this?
>
> Thanks in advance for your help! |