From:	Richard Dawe <rich AT tudor21 DOT net>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: rhide & libsocket & w98 prob
Date:	Sat, 18 Dec 1999 02:43:42 +0000
Organization:	Customer of Planet Online
Lines:	49
Message-ID:	<385AF4DE.C75D4796@tudor21.net>
References:	<1AFE428267B AT gyarab DOT cz>
NNTP-Posting-Host:	modem-89.mifepristone.dialup.pol.co.uk
Mime-Version:	1.0
X-Trace:	newsg2.svr.pol.co.uk 945536542 27552 62.136.79.217 (18 Dec 1999 17:02:22 GMT)
NNTP-Posting-Date:	18 Dec 1999 17:02:22 GMT
X-Complaints-To:	abuse AT theplanet DOT net
X-Mailer:	Mozilla 4.51 [en] (X11; I; Linux 2.2.10 i586)
X-Accept-Language:	de,fr
X-NNTP-Posting-Host:	iolanthe.tudor21.net
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Hello.

Sanda AT 97 DOT gyarab DOT cz wrote:
> I have do some libsocket programming under w98 with rhide.

I've never tried using libsocket under RHIDE.

> When I try to debug server program, there is a 80% chance
> to encounter following error. Program stops on a breakpoint, i press
> F8 or F7 to contine and screen goes blank.

This sounds like the program is blocking in a call to Windows's low-level
drivers. There's no way to abort these calls. I've tried to use
non-blocking calls as much as possible, so that the user can always break
out using Ctrl+C. If you are using connect() with the Winsock 2 interface
(via sock.vxd), then it will block until a connection is established.

> If I use just a window there is a cursor visible, in full screen not
> even that. Otherwise program is obviousky working, reacting to keys
> and such. Rhide afterwards works too, but screen is blank.

That's weird. How can you tell if the program is working if only the
cursor is visible. How does the program react to keys?

Personally, I wouldn't say that RHIDE is working if you can't see its
output ;)

> Only happens with libsocket and I suspect only in app where I listen
> on some port.

Could you find out for sure which type of app it is?

> Server sometimes crashes w98 (that's a flaw in winsock2 right ?).

Possibly. I've never used libsocket on Windows '98 (I don't have it).
Sometimes it's hard to tell why programs crash. Winsock 2 is probably OK.
I suspect the problem is in libsocket or sock.vxd.

> Has anyone encountered that, is there some help
> maybe through some options in rhide...?

I suspect the problem is in libsocket. Could you send me/post your code -
this would be useful.

Bye,

-- 
Richard Dawe
richdawe AT bigfoot DOT com ICQ 47595498 http://www.bigfoot.com/~richdawe/

- Raw text -