Am 10.09.2008 um 17:32 schrieb Stefan Dösinger:
> You can attach any debugger to a Win32 process running in Wine. This
> includes Linux debuggers like gdb, [...]
As I didn't find hints on how to do this I tried myself:
** First, start gdb in the C: directory
[EMAIL PROTECTED]:/otherubuntu/home
On Wednesday 10 September 2008 10:44:09 pm Damjan Jovanovic wrote:
> For example applications don't expect to see pointers into the upper
> 1-2 GB of the 4 GB virtual memory address space because on Windows the
> kernel's memory is mapped there. But, ld-linux.so.2 could load
> libraries there, incl
On Wed, Sep 10, 2008 at 8:17 PM, <[EMAIL PROTECTED]> wrote:
> Question :
> Why does wine have to allocate all its memory at startup? re... the issue
> that is causing the ATI drivers to have such
> a fuss why not just allocate as needed? or have the ability (if its not
> there already) to sp
dbghelp supports both linux debug formats (stabs, dwarf) as well as
microsoft's one
so any debugger using dbghelp as it's debug info provide should debug
with all bells & whistles native & builtin applications
I had some success with windbg (with a an 'e' between n & d ;-)
unfortunately, http://
ubject: RE: Debugging Wine thoughts
You can
attach any debugger to a Win32 process running in Wine. This includes Linux
debuggers like gdb, or any graphical frontends, as well as Windows debuggers
like visual studio. If you built wine from source, the Linux debuggers will s
You can attach any debugger to a Win32 process running in Wine. This
includes Linux debuggers like gdb, or any graphical frontends, as well as
Windows debuggers like visual studio. If you built wine from source, the
Linux debuggers will see the Wine source. Probably they can also read the
Windows a
