http://bugs.winehq.org/show_bug.cgi?id=15436
Summary: Collect crash data Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: NEW Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: dank@kegel.com
Suggested at Wineconf 2008.
When a wine app crashes, instead of running winedbg by default, we should run a crash handler that gathers crash info and offers to upload it to the developers.
http://bugs.winehq.org/show_bug.cgi?id=15436
--- Comment #1 from Dan Kegel dank@kegel.com 2008-09-27 13:09:07 --- FWIW, here are a few open source crash reporting tools already out there, see http://en.wikipedia.org/wiki/Crash_reporter Maybe we could reuse one of them.
http://bugs.winehq.org/show_bug.cgi?id=15436
--- Comment #2 from Vitaliy Margolen vitaliy@kievinfo.com 2008-09-27 14:46:02 --- That would be useless since it will depend on the particular binaries user has. I'd suggest to close is as won't fix. What we really should have is properly working memdump of programs that use. And full support of it with winedbg that actually works.
http://bugs.winehq.org/show_bug.cgi?id=15436
--- Comment #3 from Dan Kegel dank@kegel.com 2008-09-27 16:16:28 --- Thought of that already! We can turn it off by default, and packagers can turn it on and point it to their own crash log collector.
This was suggested by consensus at wineconf 2008, so I don't think we should dismiss it out of hand.
http://bugs.winehq.org/show_bug.cgi?id=15436
--- Comment #4 from Vitaliy Margolen vitaliy@kievinfo.com 2008-09-28 11:20:24 --- Then packagers will need provide debug symbols for all Wine versions they distribute.
Also I don't think we need to go too far for this - it's already part of Wine - an ability to save memdump. Just need to make it work reliably and be able to work with it.
http://bugs.winehq.org/show_bug.cgi?id=15436
Vincent Povirk madewokherd@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |madewokherd@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=15436
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|CVS/GIT |1.1.5
http://bugs.winehq.org/show_bug.cgi?id=15436
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download
--- Comment #5 from Austin English austinenglish@gmail.com 2010-03-11 16:04:09 --- Still present.
http://bugs.winehq.org/show_bug.cgi?id=15436
Vincent Povirk madewokherd@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|madewokherd@gmail.com |
http://bugs.winehq.org/show_bug.cgi?id=15436
butraxz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |butraxz@gmail.com
--- Comment #6 from butraxz@gmail.com 2012-05-18 05:51:20 CDT --- This bug has not been updated for two years and OP by four. Is this still an issue i current (1.5.4) or newer wine ? You may also close this as abandoned if you feel that that this is issue is no longer relevant to you.
https://bugs.winehq.org/show_bug.cgi?id=15436
--- Comment #7 from Austin English austinenglish@gmail.com --- We now have a crash reporter that offers to save the backtrace for the user (instead of always going to stderr).
No upload support, however.
https://bugs.winehq.org/show_bug.cgi?id=15436
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source Component|-unknown |winedbg
--- Comment #8 from Ken Sharp imwellcushtymelike@gmail.com --- No change.
https://bugs.winehq.org/show_bug.cgi?id=15436
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net Summary|Collect crash data |Add feature to winedbg | |crash reporter to | |optionally upload the crash | |report data to predefined | |location
--- Comment #9 from Anastasius Focht focht@gmx.net --- Hello folks,
refining summary to reflect the current state.
I suggest you really clarify your feature request. Put up some detailed definitions and requirements.
Generally spoken, by providing an upload feature you're essentially implying that someone will take care of it.
I seriously doubt this will work out in reality. The upload site will turn into a dump site for gazillion crash reports (with many being useless) and no one is really going to look at all of them.
The only feasible way to tackle a large influx of crash dumps would be to write a sophisticated piece of software that automatically analyses the crash reports, looking for common/predefined crash patterns, doing some prerequisite validation (Wine version, prefix) etc. This would result in further pre-defined/automated/scripted actions.
But again ... whom does this help?
Regards
https://bugs.winehq.org/show_bug.cgi?id=15436
Detlef Riekenberg wine.dev@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wine.dev@web.de
https://bugs.winehq.org/show_bug.cgi?id=15436
Nimo nimoshaien123@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nimoshaien123@gmail.com
-
wine-bugs＠winehq.org