-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
Am Wed, 18 Apr 2007 07:11:28 -0600 schrieb Vitaliy Margolen wine-devel@kievinfo.com:
Stephan Hermann wrote:
- What do you need from us (Ubuntu) to get better backtraces
when wine crashes (especially wine-preloader)
As Marcus mentioned the best trace you can get is from the Wine's own debugger. Of course it would be even better with debug symbols installed on the system.
- How can we work together in a better way? (e.g.
crashreport will be filed in launchpad (http://www.launchpad.net) automatically, can we file a bugreport automatically in your bugzilla?)
I would say NO. Wine crashes all the time for a lots of reasons. Some of those reasons have nothing to do with Wine itself. Some times they are a result of the missing feature. Creating bug-report for each crash won't help anyone, but will deplete resources of the server hosting bugzilla.
Looking at your test report, it's bug # 219 in Wine's bugzilla. No crash report is require there. It's enough to see "secdrv.sys" and mentioning of the ntoskrnl.exe.
In general the most useful pieces of information are ... complete terminal output, $PWD and the command used to start an application. Also the exact Wine version $(wine --version), and where did it came from (self-compiled or binary). All of them are absent from the report.
That's one report generated by apport, which is, as you and others were writing, totally useless (that was my first impression, too)
So, I'll go back to normal business for bugreporting and pointing the users to winedbg.
Thx for all your answers :)
Regards,
\sh
- -- Stephan Hermann Ubuntu Developer http://launchpad.net/~shermann shermann@ubuntu.com