Opened 10 years ago
Last modified 3 years ago
#554 new defect
provoking ARB fatal error does not cause termination
Reported by: | westram | Owned by: | devel |
---|---|---|---|
Priority: | major | Milestone: | arb7.x |
Component: | no idea | Version: | SVN |
Keywords: | Cc: |
Description (last modified by westram)
Change History (6)
comment:1 Changed 10 years ago by westram
comment:2 Changed 10 years ago by epruesse
I think unrelated.
The error is triggered in gbcmc_open and passed down into load_and_startup_main_window, where it is ignored:
NT_main.cxx:204
GB_ERROR problem = startup_mainwindow_and_dbserver(aw_root, autorun_macro); aw_message_if(problem); // no need to terminate ARB
Thereafter, the main loop simply continues to run w/o window.
I'm not sure what exactly is going on there. The startup of NT is split into a gazillion functions, so I cannot tell, what terminating on problem!=NULL would mean. It looks like macro replay is also done here (maybe NT is doing too many different things?), which is probably why the error is deemed non-fatal.
comment:3 Changed 9 years ago by westram
- Milestone set to arb6.1
comment:4 Changed 9 years ago by westram
- Description modified (diff)
- Summary changed from provoking ARB fatal error blocks launcher to provoking ARB fatal error does not cause termination
comment:5 Changed 9 years ago by westram
- Description modified (diff)
comment:6 Changed 3 years ago by westram
- Milestone changed from arb6.1 to arb7.x
move open tickets before release
Note: See
TracTickets for help on using
tickets.
Console output:
Process
: