http://bugs.winehq.org/show_bug.cgi?id=7448
------- Additional Comments From jisakiel@yahoo.es 2007-18-02 16:31 ------- OK, from what I seem to understand from the debugging, the backtrace starts in some address not available, even on the second one which is the one I did with -ggdb, which should* be equivalent to -g.
88 0x7edc6f61 in user32 (+0x6f61) (0x0045e220) 89 0x0000c030 (0x00010028) 90 0x00000000 (0x00000000) 0x7d32734e: -- no code accessible --
And the same on the last one. So I guess to see where it explodes I should not strip binaries in my whole system... Should you guys allow me to find a more convenient way to do it than recompiling the whole system, I'd be infinitely grateful for the patience invested... First time I report something like this, you know. I just found http://www.gentoo.org/proj/en/qa/backtraces.xml, which suggest adding a "nostrip" flag, and I guess recompiling the relevant packages , which I hope to be wine and its inmediate list of dependences (though that can take a while).
So again, thanks for the patience to this n00b and the pointers on how to report... I'll try to get a debugging output without that dreaded "no code accessible" line and report as soon as I can.