Article View: borland.public.cppbuilder.nativeapi
Article #14654Corrupted memory?
From: Chris
Date: Wed, 06 Aug 2003 02:48
Date: Wed, 06 Aug 2003 02:48
16 lines
1464 bytes
1464 bytes
I have an OnRead event for my server socket. It calls a function, somewhere in this function I call ReceiveBuf. No matter how I call it, even like this Socket->ReceiveBuf(NULL,NULL); or void* mem = malloc(5); Socket->ReceiveBuf(mem,4); free(mem); It causes the function to completely stop being executed, and it generates a new OnRead event. Either that or it would be choosing at that exact moment consistently to cause another OnRead event and run the function again, but is that even possible? Could an explanation be, somewhere I've corrupted my program's memory?
Technical Details
Message-ID:
<3f306c8f@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!sn-xit-09!supernews.com!newshosting.com!news-xfer2.atl.newshosting.com!newsfeed.wirehub.nl!news.kweb.on.ca!KWeb!newsgroups.borland.com!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10cc67,6183e4bd87974955,start X-Google-Attributes: gid10cc67,public X-Google-ArrivalTime: 2003-08-05 19:51:31 PST From: "Chris" <Chris8852@adelphia.net> Newsgroups: borland.public.cppbuilder.nativeapi Subject: Corrupted memory? Date: Tue, 5 Aug 2003 22:48:46 -0400 Lines: 18 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 NNTP-Posting-Host: 68.65.164.124 Message-ID: <3f306c8f@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1060138127 68.65.164.124 (5 Aug 2003 19:48:47 -0700) Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!sn-xit-09!supernews.com!newshosting.com!news-xfer2.atl.newshosting.com!newsfeed.wirehub.nl!news.kweb.on.ca!KWeb!newsgroups.borland.com!not-for-mail