X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f Message-ID: <3CAA5C53.6020805@vif.com> From: Sahab Yazdani Organization: PheonixSoft Interactive User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.9+) Gecko/20020328 X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.os.msdos.djgpp Subject: DOS/Windows Pointer Corruption Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cache-Post-Path: www.vif.com!unknown AT ip216-239-69-147 DOT vif DOT net X-Cache: nntpcache 2.4.0b4 (see http://www.nntpcache.org/) Lines: 33 NNTP-Posting-Date: Tue, 02 Apr 2002 19:37:53 CST X-Trace: sv3-lzZRV2J7ghZSk+AyGHRpMRlWKTBtKuBwSy8xPMztukUpQWc8fQLyweka9+hqx8x5a5xoIegcqqiAxN4!q6ZqG+Wunq161hCuP0RCZhq204tz+qyvClRvlErOnABCm36MIlKO22w= X-Complaints-To: abuse AT GigaNews DOT Com X-DMCA-Notifications: http://www.giganews.com/info/dmca.html X-Abuse-Info: Please be sure to forward a copy of ALL headers X-Abuse-Info: Otherwise we will be unable to process your complaint properly Date: Wed, 03 Apr 2002 01:37:53 GMT To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com okay, first off I know that if my program is working fine in Windows but not in DOS it usually means that there are pointer bugs in my program, BUT, i have initialized a VESA2.0 screen (which returns a pointer to RAM that acts as the primary draw surface) which I am %110 sure that the pointer is valid (cuz after all, i can draw on it in Windows and actually see the results) and then I try to clear it to black via this call: memset( memPtr, 0, width*height*bitDepth>>3 ); now on windows this works fine, but on plain DOS it chokes on this exact line (via symify). nothing else is happening to the pointer as I printf-ed its location right before memset-ting it... i have also tried reducing the amount of memory it zeroes by changing width, height, and bitDepth to smaller numbers but to no avail. so what is the dealeo? thnx for any help which you may provide. PS. why doesn't symify give line numbers on a traceback anymore?? it still gives function names (although mangled up cuz of C++) and filenames, but the line number is always 0 now. i guess it has something to do with my upgrading to GCC 3.0.3? any fixes?? -- ************************************************************** * Sahab Yazdani * "Lisa, in this house we obey the laws of * * Thornhill S.S * thermodynamics!" - Homer Simpson * ************************************************************** * http://pheonixsoft.virtualave.net/ * :) * **************************************************************