On Thu, 3 Mar 2005 20:31:28 +0100 Christian Biere <[EMAIL PROTECTED]> wrote: > The Blue Meanie wrote: > > (still had to remove the blank lines from the Makefiles, but no biggie). > > Those should be removed now but those files are generated so the generator > would need to be fixed. > Considering how easy this is to do, I'm not stressing it. But I'll watch to see if it stops at some point. :) I'm quite happy with how simple the config/make cycle is for me. I'm used to a LOT more hoops.
> > ** ERROR **: file glib-missing.c: line 377: assertion failed: > > (strlen(buf) < FILENAME_MAXBYTES) > > I assume this is fixed as well now but it would be good if you could > post the contents of "buf" or at least verify that the first character > is a dot to confirm that I fixed the same bug. > Ok, I'd be happy to check this, but... I'm quite the gdb n00b. Is this something I can extract from the core? Or do I need to reproduce the problem? If I can get it from the core, exactly what syntax do I need to use in gdb to get the info? Sorry if these are lame questions, I haven't used gdb much beyond simple stack traces (although I did play around with using it to catch signals once). Cheers, The Blue Meanie ([EMAIL PROTECTED]) ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Gtk-gnutella-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
