-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-Type: text/plain; charset=us-ascii
In a message dated: Wed, 24 Apr 2002 11:32:38 EDT Michael O'Donnell said: >Ha! I haven't analyzed this yet (and might never) but running bash >under GDB (actually, I attached GDB to the child bash proc) yields: > > > Program received signal SIGABRT, Aborted. > 0x400497b1 in kill () from /lib/libc.so.6 > (gdb) where > #0 0x400497b1 in kill () from /lib/libc.so.6 > #1 0x40049494 in raise () from /lib/libc.so.6 > #2 0x4004ac11 in abort () from /lib/libc.so.6 > #3 0x0806c27d in programming_error () at error.c:258 > #4 0x080acd69 in xbotch (mem=0x8229148, e=4, > s=0x80c3020 "free: underflow detected; mh_nbytes out of range", > file=0x80b1e19 "array.c", line=78) at malloc.c:286 Please excuse my naivety of understanding GDB traces. I'm interpreting this as an out-of-memory error as a result of too many file names filling up an array? Is that an accurate interpretation of this trace? If so, why would you use an array for this sort of thing. Way back in time when I was taking Intro to Programming, they taught us to use linked lists for this type of scenario where you didn't know up front how many items you'd need to store. I know there's usually a huge disconnect between "How things are taught" and "How things are". Is this the situation here? Why? What are the pros/cons of using arrays vs. linked lists in this type of scenario? Please help me be less ignorant :) Thanks, - -- Seeya, Paul -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Exmh version 2.2 06/23/2000 (debian 2.2-1) iD8DBQE8xtOQuweSOVPxKO4RAs0hAJ9otRPX1CxOZgGjRk8sWCeDvhAregCfcl2h DGXcW0P1kgYxtcAnqJqJPk0= =mduj -----END PGP SIGNATURE----- ***************************************************************** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the text 'unsubscribe gnhlug' in the message body. *****************************************************************
