Mail Archives: djgpp/2000/08/29/20:15:12
>> a. the gstring class: it crashes with SIGSEGV while strcpy()'ing the
>> argument of the constructor into the classes char * but the log file
>> does not contain any entries by YAMD.
>
>What entries by YAMD did you expect?
Well, it crashes at a point that is perfectly normal when compiled
with GCC, so I thought it would also make an 'ERROR' entry into its
log file or something *shrugs*.
>> b. CFG library's test.c : YAMD finds 3 memory leaks, one in LIBC or so
>> it seems !!
>>
>> WARNING: Memory leak
>> Address 0x17f000, size 16384
>> Allocated by malloc at
>> BEGIN TRACEBACK
>> 0x00012e63 __flsbuf+67
>
>This is not a memory leak:
I thought so, but mentioned it anyways.
>> Shutting down Allegro
>> Exiting due to signal SIGSEGV
>> Page fault at eip=00056e10, error=0004
>
>error=0004 means the program tried to read from an address that is
>outside allocated limits.
>
>I'd say, forget the second crash for a while and concentrate on the
>first one, it looks like a real bug. When you solve the first
>problem, rerun the program and see if there's more.
I added the allegro_init() function to an other program with the same
result. It got in a loop inside the get_config_string() function and
crashed. So it's definitely something inside Allegro and not related
to my code.
On the other hand someone who uses Linux told me he doesn't have any
problems with Allegro/YAMD which either means it's a DOS related
problem or my computer doesn't like YAMD very much :-<
But I did do some serious debugging (not using YAMD) and found out
that I had overlooked something inside the doubly linked list code...
*bashes head against wall*... and since then my program doesn't crash
any more :->
Thanks for your help,
Bernd
- Raw text -