re: Debugging applications running on wine

[Dan Kegel]

Kevin K wrote:
> Is winedbg the only method of debugging applications being
> developed for Windows on Wine?
>
> For instance, assume a program developed with Visual Studio
> in C or C++, and I needed to debug it on Linux?

If winedbg doesn't work for you, we should fix it.   Same
goes for other debuggers.

For instance, ollydbg seems to work
http://appdb.winehq.org/objectManager.php?sClass=application&iId=2619

Visual C++ 6's debugger seems to work at least a little, too:
http://appdb.winehq.org/objectManager.php?sClass=version&iId=31

Please file bugs for any problems you run into.
- Dan

socket errors...

[Chris Ahrendt]

I started narrowing down some information in debugging a winemm issue 
and noticed the following in my logs...

trace:winsock:WSARecvFrom socket 00e8, wsabuf 0x33f638, nbufs 1, flags 
0, from 0x33f67c, fromlen 16, ovl (nil), func (nil)
trace:winsock:WSARecvFrom fd=51, options=0
warn:winsock:WSARecvFrom  -> ERROR 10035

The 10035 is a buffer overflow error (I think)

and I don't know much if at all how this set of code is supposed to 
work... anyone else getting this with the latest git tree?

and any help on figuring out why the buffer is getting this error...

thanks

Chris

socket errors...

[James Hawkins]

On Mon, Sep 8, 2008 at 10:03 PM, Chris Ahrendt  wrote:
> I started narrowing down some information in debugging a winemm issue
> and noticed the following in my logs...
>
> trace:winsock:WSARecvFrom socket 00e8, wsabuf 0x33f638, nbufs 1, flags
> 0, from 0x33f67c, fromlen 16, ovl (nil), func (nil)
> trace:winsock:WSARecvFrom fd=51, options=0
> warn:winsock:WSARecvFrom  -> ERROR 10035
>
> The 10035 is a buffer overflow error (I think)
>
> and I don't know much if at all how this set of code is supposed to
> work... anyone else getting this with the latest git tree?
>
> and any help on figuring out why the buffer is getting this error...

A little context might help...I, for one, have no idea what you're
talking about.

socket errors...

[Chris Ahrendt]

James Hawkins wrote:
> On Mon, Sep 8, 2008 at 10:03 PM, Chris Ahrendt  wrote:
> > I started narrowing down some information in debugging a winemm issue
> > and noticed the following in my logs...
> >
> > trace:winsock:WSARecvFrom socket 00e8, wsabuf 0x33f638, nbufs 1, flags
> > 0, from 0x33f67c, fromlen 16, ovl (nil), func (nil)
> > trace:winsock:WSARecvFrom fd=51, options=0
> > warn:winsock:WSARecvFrom  -> ERROR 10035
> >
> > The 10035 is a buffer overflow error (I think)
> >
> > and I don't know much if at all how this set of code is supposed to
> > work... anyone else getting this with the latest git tree?
> >
> > and any help on figuring out why the buffer is getting this error...
>
> A little context might help...I, for one, have no idea what you're
> talking about.

ok context.. I turned on tracing for winsock while trying to narrow down 
another issue I am working on. When I did... I started seeing these 
errors in my output where I had not before... (IE turn +winsock off does 
not output the above)

Chris

socket errors...

[Damjan Jovanovic]

On Tue, Sep 9, 2008 at 5:03 AM, Chris Ahrendt  wrote:
> I started narrowing down some information in debugging a winemm issue
> and noticed the following in my logs...
>
> trace:winsock:WSARecvFrom socket 00e8, wsabuf 0x33f638, nbufs 1, flags
> 0, from 0x33f67c, fromlen 16, ovl (nil), func (nil)
> trace:winsock:WSARecvFrom fd=51, options=0
> warn:winsock:WSARecvFrom  -> ERROR 10035
>
> The 10035 is a buffer overflow error (I think)

No, 10035 is WSAEWOULDBLOCK, which is normal for WSARecvFrom() on
non-blocking sockets that currently have no data in the receive
buffer.
> and I don't know much if at all how this set of code is supposed to
> work... anyone else getting this with the latest git tree?
>
> and any help on figuring out why the buffer is getting this error...

I'd be more worried if it wasn't :-).
> thanks
>
> Chris

Bye
Damjan

socket errors...

Ok thanks... so its safe to ignore which is what I was wondering =)

Chris

-----Original Message-----
From: Damjan Jovanovic 
To: [e-mail]
Cc: wine-devel 
Sent: Tue, 9 Sep 2008 1:01 am
Subject: Re: socket errors...

On Tue, Sep 9, 2008 at 5:03 AM, Chris Ahrendt  wrote:
> I started narrowing down some information in debugging a winemm issue
> and noticed the following in my logs...
>
> trace:winsock:WSARecvFrom socket 00e8, wsabuf 0x33f638, nbufs 1, flags
> 0, from 0x33f67c, fromlen 16, ovl (nil), func (nil)
> trace:winsock:WSARecvFrom fd=51, options=0
> warn:winsock:WSARecvFrom  -> ERROR 10035
>
> The 10035 is a buffer overflow error (I think)

No, 10035 is WSAEWOULDBLOCK, which is normal for WSARecvFrom() on
non-blocking sockets that currently have no data in the receive
buffer.
> and I don't know much if at all how this set of code is supposed to
> work... anyone else getting this with the latest git tree?
>
> and any help on figuring out why the buffer is getting this error...

I'd be more worried if it wasn't :-).
> thanks
>
> Chris

Bye
Damjan

Debugging applications running on wine

[Kevin Krieser]

On Sep 8, 2008, at 9:36 PM, Dan Kegel wrote:
> Kevin K wrote:
> > Is winedbg the only method of debugging applications being
> > developed for Windows on Wine?
> >
> > For instance, assume a program developed with Visual Studio
> > in C or C++, and I needed to debug it on Linux?
>
> If winedbg doesn't work for you, we should fix it.   Same
> goes for other debuggers.
>
> For instance, ollydbg seems to work
> http://appdb.winehq.org/objectManager.php?sClass=application&iId=2619
>
> Visual C++ 6's debugger seems to work at least a little, too:
> http://appdb.winehq.org/objectManager.php?sClass=version&iId=31
>
> Please file bugs for any problems you run into.
> - Dan

Thanks.

This is just hypothetical right now about some future development that  
may have to support Linux, XP/Vista, and Windows Mobile.