On 03/08/2010 07:32 PM, Sven Joachim wrote:
On 2010-03-08 18:35 +0100, eric2.vale...@orange-ftgroup.com wrote:
Package: symlinks
Version: 1.2-6
Severity: normal
I have a use case where using 1.2-rel6 I hit and assertion in malloc that
does not happend when I use 1.4 version of symlinks.
Something along symlinks:malloc assert failed and a absolutely
unreadable formula. Note that compiling the same tree with a level
link less (I now have a symlink for /scratch were previously I had a
real mounted fs was working.
Note that if there is a malloc/free problem, using valgrind
On 03/09/2010 10:18 AM, VALETTE Eric RD-MAPS-REN wrote:
Something along symlinks:malloc assert failed and a absolutely
unreadable formula. Note that compiling the same tree with a level
link less (I now have a symlink for /scratch were previously I had a
real mounted fs was working.
Note
On 03/09/2010 01:06 PM, Sven Joachim wrote:
On 2010-03-09 10:29 +0100, eric2.vale...@orange-ftgroup.com wrote:
On 03/09/2010 10:18 AM, VALETTE Eric RD-MAPS-REN wrote:
Something along symlinks:malloc assert failed and a absolutely
unreadable formula. Note that compiling the
On 2010-03-09 13:15 +0100, VALETTE Eric RD-MAPS-REN wrote:
On 03/09/2010 01:06 PM, Sven Joachim wrote:
On 2010-03-09 10:29 +0100, eric2.vale...@orange-ftgroup.com wrote:
On 03/09/2010 10:18 AM, VALETTE Eric RD-MAPS-REN wrote:
Something along symlinks:malloc assert failed
On 03/09/2010 02:02 PM, Sven Joachim wrote:
I will do that anyway (might take some time to find a sponsor, though),
but I would also like to understand the problem. In case it isn't
clear: this assertion error is very weird and might just be a symptom of
a problem that has nothing to do with
On 03/09/2010 03:55 PM, Sven Joachim wrote:
On 2010-03-09 15:16 +0100, eric2.vale...@orange-ftgroup.com wrote:
Readding only the patch, the useage of the buffer returned by
get_current_dir_name may be wrong: the allocated space is by no way
equal to PATH_MAX+2 so any code making assumption
On 03/09/2010 02:16 PM, VALETTE Eric RD-MAPS-REN wrote:
a free of an address returned by a non reentrant function could
perfectly cause it (try the _r version with explicit buffer allocation)
Readding only the patch, the useage of the buffer returned by
get_current_dir_name may be wrong: the
On 2010-03-09 15:16 +0100, eric2.vale...@orange-ftgroup.com wrote:
Readding only the patch, the useage of the buffer returned by
get_current_dir_name may be wrong: the allocated space is by no way
equal to PATH_MAX+2 so any code making assumption on this may simply
fail.
There is no code
On 2010-03-09 10:29 +0100, eric2.vale...@orange-ftgroup.com wrote:
On 03/09/2010 10:18 AM, VALETTE Eric RD-MAPS-REN wrote:
Something along symlinks:malloc assert failed and a absolutely
unreadable formula. Note that compiling the same tree with a level
link less (I now have a symlink for
Package: symlinks
Version: 1.2-6
Severity: normal
I have a use case where using 1.2-rel6 I hit and assertion in malloc that
does not happend when I use 1.4 version of symlinks. As a result, compilation
of a complex source tree fails.
So please package the new version or aat leasta aggrgate
On 2010-03-08 18:35 +0100, eric2.vale...@orange-ftgroup.com wrote:
Package: symlinks
Version: 1.2-6
Severity: normal
I have a use case where using 1.2-rel6 I hit and assertion in malloc that
does not happend when I use 1.4 version of symlinks. As a result, compilation
of a complex source
12 matches
Mail list logo
