delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1999/06/02/14:43:43

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <37557AF8.51530D6C@cisco.com>
Date: Wed, 02 Jun 1999 11:42:00 -0700
From: "Ashish C. Nagre" <ashishcn AT cisco DOT com>
Reply-To: ashishcn AT cisco DOT com
Organization: Cisco Systems
X-Mailer: Mozilla 4.03 [en] (WinNT; U)
MIME-Version: 1.0
To: corinna AT vinschen DOT de, cygwin AT sourceware DOT cygnus DOT com
Subject: Please help

Hi,
I am stuck for two days now and would be really grateful if you could
help me.

My problem is as follows:

I have a function that makes an ioctl() call 
	ioctl (fd, SIOCGIFFLAGS, (char*)&ifr)
      fd is a socket handle

The flags that are returned inside the debugger gdb are 0x99 
but when I run the executable the flags returned are 0x34.
The n/w devices are loopback, ether and RAS device.

Another strange thing is that if I do the following,
	memset((char*)&ifr, 0, sizeof(ifr))

before the ioctl() call then the behaviour inside and out of gdb is the
same.
I have really no clue why this is happening and have spent way too much
time trying to figure out.
Does anyone know why this happens ?
I will be very grateful to anyone helping me out.
Thank you for your time.


Regards,
Ashish

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019