http://bugs.winehq.org/show_bug.cgi?id=21843
--- Comment #5 from Juan Lang juan_lang@yahoo.com 2010-02-26 10:30:19 --- (In reply to comment #4)
Could you please give more information on why you think they are 'clearly broken'? It is certainly not clear to me.
He means, there's no debug information about the Wine source in the backtrace. The last stack frame of your backtrace: 0 0x0059df6e FarTexDB::Setup+0x25e(hrc=(nil), path="C:\Program Files\FreeFalcon5\terrdata\korea\texture") [g:\cobradev\ffviper\graphics\texture\fartex.cpp:120] in ffviper (0x0547dc74)
That's interesting, it has source and line number information from the application itself. The first couple of stack frames:
8 0x68162ab5 (0x0547f498) 9 0x68251dce (0x00000000)
These should provide line number and source information about the Wine source. If there's a debug rpm package, please install that instead. When providing backtraces, yes, it's normal to compile Wine so that backtrace information with debug info is available.