Article View: borland.public.cppbuilder.nativeapi
Article #7017Re: Memory problems: new versus GlobalAlloc
From: Wim Bekker
Date: Wed, 23 Mar 2005 09:47
Date: Wed, 23 Mar 2005 09:47
10 lines
1358 bytes
1358 bytes
"Bob Gonder" <notbg@notmindspring.invalid> wrote: > 2) Maybe you have an overrun bug that trashes "new", but is hidden by > GlobalAlloc's looser packing. If I allocate 2 times the memory size, things get even worse! If I allocate 20 times the size, bad things happen. Wim
Technical Details
Message-ID:
<42413a89@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newshosting.com!nx01.iad01.newshosting.com!news-out.nntp.be!propagator2-sterling.newsfeeds.com!news-in.newsfeeds.com!in.nntp.be!caladan.landsraad.net!newsgroups.borland.com!not-for-mailReferences:
<42403f3c@newsgroups.borland.com> <c1m141hh73nrcsk12s13ued80o2fgv2u4v@4ax.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 10cc67,6b3a605b9bc38024 X-Google-Attributes: gid10cc67,public X-Google-Language: ENGLISH,ASCII-7-bit From: "Wim Bekker" <no-no-no-mail@no-no-noware.com> Newsgroups: borland.public.cppbuilder.nativeapi References: <42403f3c@newsgroups.borland.com> <c1m141hh73nrcsk12s13ued80o2fgv2u4v@4ax.com> Subject: Re: Memory problems: new versus GlobalAlloc Date: Wed, 23 Mar 2005 10:47:34 +0100 Lines: 12 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2180 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 NNTP-Posting-Host: 82.161.70.62 Message-ID: <42413a89@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1111571081 82.161.70.62 (23 Mar 2005 01:44:41 -0800) Path: arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newshosting.com!nx01.iad01.newshosting.com!news-out.nntp.be!propagator2-sterling.newsfeeds.com!news-in.newsfeeds.com!in.nntp.be!caladan.landsraad.net!newsgroups.borland.com!not-for-mail