On Sat, Jun 03, 2006 at 05:38:25PM -0300, Kroty wrote:
Hi folks,
I'm running OpenBSD 3.9 and I have a program that is giving
some unexpected output.
But, if I run it with MALLOC_OPTIONS=G, I works fine.
What does it mean? I've read the malloc(3) manpage, but
I don't quite understand what
On 6/3/06, Kroty [EMAIL PROTECTED] wrote:
Hi folks,
I'm running OpenBSD 3.9 and I have a program that is giving
some unexpected output.
But, if I run it with MALLOC_OPTIONS=G, I works fine.
What does it mean? I've read the malloc(3) manpage, but
I don't quite understand what the G option does.
Nick Guenther wrote:
On 6/3/06, Kroty [EMAIL PROTECTED] wrote:
Hi folks,
I'm running OpenBSD 3.9 and I have a program that is giving
some unexpected output.
But, if I run it with MALLOC_OPTIONS=G, I works fine.
What does it mean? I've read the malloc(3) manpage, but
I don't quite understand
On 6/4/06, Kroty [EMAIL PROTECTED] wrote:
Nick Guenther wrote:
On 6/3/06, Kroty [EMAIL PROTECTED] wrote:
Hi folks,
Hi,
thanks for your reply.
I've run the program with MALLOC_OPTIONS=AFPG and it doesn't
crash at all.
In fact, it works fine if I run it with the G, but if I run it
with g, it
Hi folks,
I'm running OpenBSD 3.9 and I have a program that is giving
some unexpected output.
But, if I run it with MALLOC_OPTIONS=G, I works fine.
What does it mean? I've read the malloc(3) manpage, but
I don't quite understand what the G option does.
Could you please give me some more
5 matches
Mail list logo