Opened 11 years ago
Closed 11 years ago
#391 closed enhancement (implemented)
add bug report generator to arb_launch
| Reported by: | epruesse | Owned by: | westram |
|---|---|---|---|
| Priority: | normal | Milestone: | arb6 |
| Component: | no idea | Version: | SVN |
| Keywords: | Cc: |
Description (last modified by westram)
Since we now have a wrapper program around the ARB binaries, this might be an easy point to catch data when ARB crashes and simplify filing a 
report.
Things to catch:
- build number
- SVN revision & branch (output of arb_ntree --help should suffice)
- OS info lsb_release -a
- Kernel info uname -a
- Memory info free
- console output (stack trace)
- also include stack traces of client apps (edit4,…). Maybe always save to unique-named logs and collect all existing logs before arb (script) terminates.
Change History (5)
comment:1 Changed 11 years ago by westram
- Milestone set to arb6
comment:2 Changed 11 years ago by westram
- Description modified (diff)
comment:3 follow-up: ↓ 4 Changed 11 years ago by epruesse
comment:4 in reply to: ↑ 3 Changed 11 years ago by westram
- Owner changed from devel to westram
- Status changed from new to assigned
comment:5 Changed 11 years ago by westram
- Resolution set to implemented
- Status changed from assigned to closed
by [11754]
Note: See
TracTickets for help on using
tickets.
How about catching the entire console output via tee?
It's not all going to be crashes with stack trace, and the log will help. User should be informed, that there might be private data in there, though, and it cannot go directly into a ticket for the same reason.