Re: 1.3.22-1 on XP: malloc returns overlapping buffers

2003-08-23 Thread Russell O'Connor
Corinna Vinschen writes: > > That should be fixed for the next release. > > Thanks for the testcase, > Corinna You're welcome. Thanks for the fast fix. You folks are absolutely amazing. Russ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygw

Re: 1.3.22-1 on XP: malloc returns overlapping buffers

2003-08-23 Thread Corinna Vinschen
On Thu, Aug 21, 2003 at 04:27:39PM +0200, Corinna Vinschen wrote: > On Thu, Aug 21, 2003 at 08:45:12AM -0400, roconnor wrote: > > On Wed, Aug 20, 2003 at 11:12:27PM -0400, Larry Hall wrote: > > > > > This works OK for me on W2K SP1 with cygwin 1.5.x. Maybe you want to > > > upgrade to this (i.e.

Re: 1.3.22-1 on XP: malloc returns overlapping buffers

2003-08-22 Thread Ljubomir Josifovski
On Thu, Aug 21, 2003 at 06:49:44PM +0100, Ljubomir Josifovski wrote: > > Win2K, 512MB RAM, cygwin 1.3.22. Forgot to attach my cygcheck.out. -- Ljubomir Josifovski Cygwin Win95/NT Configuration Diagnostics Current System Time: Thu Aug 21 18:46:53 2003 Windows 2000 Professional Ver 5.0 Build 21

RE: 1.3.22-1 on XP: malloc returns overlapping buffers

2003-08-21 Thread Hannu E K Nevalainen \(garbage mail\)
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf > Of roconnor > I am finding that under some circumstances a buffer returned by malloc > will overlap with a buffer returned by a previous call to malloc that > has not been freed. I was able to reduce it to the following test > case. Ru

Re: 1.3.22-1 on XP: malloc returns overlapping buffers

2003-08-21 Thread Ljubomir Josifovski
On Wed, Aug 20, 2003 at 04:07:11PM -0400, roconnor wrote: > I am finding that under some circumstances a buffer returned by malloc > will overlap with a buffer returned by a previous call to malloc that > has not been freed. I was able to reduce it to the following test > case. Running under cygw

Re: 1.3.22-1 on XP: malloc returns overlapping buffers

2003-08-21 Thread Corinna Vinschen
On Thu, Aug 21, 2003 at 08:45:12AM -0400, roconnor wrote: > On Wed, Aug 20, 2003 at 11:12:27PM -0400, Larry Hall wrote: > > > This works OK for me on W2K SP1 with cygwin 1.5.x. Maybe you want to > > upgrade to this (i.e. the test version) and see if you still see the > > problem. > > > > I sti

Re: 1.3.22-1 on XP: malloc returns overlapping buffers

2003-08-21 Thread roconnor
On Wed, Aug 20, 2003 at 11:12:27PM -0400, Larry Hall wrote: > This works OK for me on W2K SP1 with cygwin 1.5.x. Maybe you want to > upgrade to this (i.e. the test version) and see if you still see the > problem. > I still see the problem on both XP and W2K with cygwin 1.5.2-1. Maybe it's rel

Re: 1.3.22-1 on XP: malloc returns overlapping buffers

2003-08-20 Thread Larry Hall
roconnor wrote: I am finding that under some circumstances a buffer returned by malloc will overlap with a buffer returned by a previous call to malloc that has not been freed. I was able to reduce it to the following test case. Running under cygwin 1.3.22-1 on Windows XP Professional Version 200

Re: 1.3.22-1 on XP: malloc returns overlapping buffers

2003-08-20 Thread Larry Hall
roconnor wrote: I am finding that under some circumstances a buffer returned by malloc will overlap with a buffer returned by a previous call to malloc that has not been freed. I was able to reduce it to the following test case. Running under cygwin 1.3.22-1 on Windows XP Professional Version 20

Re: 1.3.22-1 on XP: malloc returns overlapping buffers

2003-08-20 Thread Rolf Campbell
Unable to reproduce using Win2000 SP4 (cygwin 1.5.2). roconnor wrote: I am finding that under some circumstances a buffer returned by malloc will overlap with a buffer returned by a previous call to malloc that has not been freed. I was able to reduce it to the following test case. Running under

1.3.22-1 on XP: malloc returns overlapping buffers

2003-08-20 Thread roconnor
I am finding that under some circumstances a buffer returned by malloc will overlap with a buffer returned by a previous call to malloc that has not been freed. I was able to reduce it to the following test case. Running under cygwin 1.3.22-1 on Windows XP Professional Version 2002 SP1 it reports