On 15:32 09 Jul 2002, Daniel Senderowicz <[EMAIL PROTECTED]> wrote: | I'm new to linux and this list, so please bear with me if this | problem was already posted before. | I compiled a program that opens a few files with fopen and fclose. | When I run it it gives some segmentation faults. According to gdb, | the problem appears when fopen/fclose in turn call some malloc/free | functions. This is confirmed when I set MALLOC_CHECK_=1, that | mentions something abount a bad pointer to free(). This program | runs perfectly on a NetBSD machine (mips), so I'm wondering if that | is a particular problem of linux, or the gnu library and if there | is a solution for that. Thanks in advance.
Without seeing the source we can't say. Properly used, fopen/fclose are perfectly portable. I'd say you don't something wrong. But not being psychic we can't tell you what without seeing the code! -- Cameron Simpson, DoD#743 [EMAIL PROTECTED] http://www.zip.com.au/~cs/ A clean desk is the sign of a blank mind. _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
