Opened 14 years ago
Last modified 6 years ago
#313 new enhancement/feature request
make navit optionally log the gdb crash backtrace
Reported by: | Udo | Owned by: | KaZeR |
---|---|---|---|
Priority: | major | Milestone: | version 0.6.0 |
Component: | core | Version: | git master |
Severity: | complex | Keywords: | gdb, segfault, logging |
Cc: |
Description
make navit optionally log the gdb crash backtrace
Change History (4)
comment:1 Changed 12 years ago by kazer
- Milestone set to version 0.3.0
comment:2 Changed 10 years ago by usul
- Keywords gdb segfault logging added
- Milestone changed from version 0.5.0 to version 0.5.1
IMHO both would be useful:
- stderror - notify user
- .log - save it for a bug report
Providing users an better way to help us on finding hard bugs is an essential requirement. So I scheduled it for the next hotfix release.
comment:3 Changed 6 years ago by http://wiki.navit-project.org/index.php/user:jkoan
- Severity set to complex
I think we should log real errors to files in a directory and send them on the next start of navit right before navit really starts. For the upload we need to think about a mechanisem that is working every time (while network is available) and is handy for us.
comment:4 Changed 6 years ago by http://wiki.navit-project.org/index.php/user:jkoan
- Milestone changed from version 0.5.1 to version 0.6.0
Note: See
TracTickets for help on using
tickets.
log, to the screen? or to a file?