http://bugs.winehq.org/show_bug.cgi?id=15496 --- Comment #15 from Jeff Zaroyko <jeffz(a)jeffz.name> 2009-09-07 04:41:04 --- (In reply to comment #14)
Second of all, I have no idea how to create a backtrace with debug symbols. I have a wine-debuginfo package installed, after your first reply, which contains files like:
/usr/lib/debug/usr/lib/wine/d3drm.dll.so.debug /usr/lib/debug/.build-id/ad/d3fcb4573c67fce5bc1a5dc054f3a157bdd4b2.debug /usr/lib/debug/usr/bin/winecpp.debug
I followed the instructions at http://wiki.winehq.org/Backtraces and got the information I pasted in the comment above.
If there's a step I missed, please point me to the documentation or post instructions here and I'll be happy to follow them and update the wiki documentation.
It could be that the debug symbols aren't complete, normally what you'd expect to see in a backtrace is the arguments to the function calls in the backtrace. Simplest thing to do would be to compile Wine from source, probably by getting a copy of the code from git and building that. There is http://wiki.winehq.org/GitWine , http://wiki.winehq.org/WineOn64bit (if you're using a 64bit distro) and the README - if you need further help setting up / compiling, the forum is a good place to start rather than requesting further help here with the basics. Once you have that, you'll be able to provide much better bug reports. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.