https://bugs.winehq.org/show_bug.cgi?id=52790
--- Comment #5 from Eric Pouech eric.pouech@orange.fr --- Getting back to this one...
perhaps I've been a bit too optimistic :-(
when I get these messages: - it's always on a 32bit debuggee - and the info we can't grok is always the very same pattern
Unfortunately, I don't see a way to integrate that computing into the dbghelp API structure
Not that the computation is not doable - all the required code is already in place - but we need the actual CPU context which isn't passed as input parameter in these offending dbghelp requests
Anyway, I want to be sure that I didn't miss some other situations: - can you confirm it's only 32bit for the time being? - if possible can you retry with the attached patch: + it should silence output (changing error in backtrace from internal to can't compute; it doesn't make a difference for the user, but it's a bit clearer) + but generate output if it doesn't match the only pattern I've encountered; just to check what could be done