How can I get a stack trace in case of an assertion failure? There is no core left. Perhaps replacing the exit of the assert with an instructions that does generate a core dump (like trying to write something to an illegal address)?
I can add that it seems a kind of random. It does not happen at the same point in the checksum after GTKG restart and other checksums may be completed without a flaw. Looks like a memory corruption/lack of initialization?... Let me know how to proceed. Thanks for the help. Mihai On 23 Jun 2003, Raphael Manfredi wrote: > Quoting "Mihai T. Lazarescu" <[EMAIL PROTECTED]> from ml.softs.gtk-gnutella.devel: > :assertion failed: (d->status == GTA_DL_VERIFYING) > : aborting... > : > :I use the latest CVS on RedHat 9, compiled with gcc > :3.2.2. Please let me know if I can help more. > > The stack trace would help tremendously see a common pattern between all > those bugs... > > Raphael ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Gtk-gnutella-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
