[uClibc 0001493]: fopen(<filenam>, "a") or "w" causes crash. The gdb data follows:

[bugs at busybox.net]

The following issue has been CLOSED 
====================================================================== 
http://busybox.net/bugs/view.php?id=1493 
====================================================================== 
Reported By:                akennedy
Assigned To:                uClibc
====================================================================== 
Project:                    uClibc
Issue ID:                   1493
Category:                   Other
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     closed
Resolution:                 unable to reproduce
Fixed in Version:           
====================================================================== 
Date Submitted:             09-06-2007 18:44 PDT
Last Modified:              12-30-2007 12:34 PST
====================================================================== 
Summary:                    fopen(<filenam>, "a") or "w" causes crash.  The gdb
data follows:
Description: 
http://busybox.net/bugs/view.php?id=0  0x0805d17f in __malloc_consolidate ()
(gdb) backtrace
http://busybox.net/bugs/view.php?id=0  0x0805d17f in __malloc_consolidate ()
http://busybox.net/bugs/view.php?id=1  0x0805c65d in malloc ()
http://busybox.net/bugs/view.php?id=2  0x0805a98f in _stdio_fopen ()
http://busybox.net/bugs/view.php?id=3  0x0805a61e in fopen ()

====================================================================== 

---------------------------------------------------------------------- 
 akennedy - 09-07-07 07:36  
---------------------------------------------------------------------- 
This error seems to be only in the file:
libc/stdlib/malloc-standard/free.c
because when I changed to the simple-malloc, I no longer get the segfault. 

---------------------------------------------------------------------- 
 vapier - 12-30-07 12:34  
---------------------------------------------------------------------- 
you'll need to actually describe your setup.  what uClibc version ?  what
architecture ?

you should also post a small test case that exhibits the problem.  if
fopen() was as broken as you describe, i imagine a lot more people would
notice. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
09-06-07 18:44  akennedy       New Issue                                    
09-06-07 18:44  akennedy       Status                   new => assigned     
09-06-07 18:44  akennedy       Assigned To               => uClibc          
09-06-07 19:07  akennedy       Issue Monitored: akennedy                    
09-07-07 07:36  akennedy       Note Added: 0002726                          
12-30-07 12:34  vapier         Note Added: 0003339                          
12-30-07 12:34  vapier         Status                   assigned => closed  
12-30-07 12:34  vapier         Resolution               open => unable to
reproduce
======================================================================