Ludovic Brenta wrote: > Kevin Brown <[EMAIL PROTECTED]> writes: > > Sounds like I'll wanna grab the current source, but it also sounds > > like the changes you made and the changes I made are quite similar. > > Yes, and I just uploaded 4.0.1 which, according to its change log, > fixes a few bugs, but not the ones we're interested in. The patches > from 4.0.0 applied cleanly, but I also had to add a small patch for > GtkAda 2.8.1. > > With both 4.0.0 and 4.0.1, I get slightly different symptoms from you: > > (1) GPS hangs, but does not crash, when trying to open a file > selector. I too suspect something wrong in GtkAda. Unfortunately > there is no unit test for the file selector. Maybe it would be > worthwhile to write one. (unless I missed something in testgtk? > Look in /usr/share/doc/libgtkada2-doc/examples/testgtk.tar.gz)
Hmm...it still crashes on me, consistently. I get the following message: *** glibc detected *** corrupted double-linked list: 0x0000000001b39820 *** Aborted > > ==22897== Invalid read of size 8 > > ==22897== at 0x601684E: > > system__finalization_implementation__attach_to_final_list (in > > /usr/lib/libgnat-4.1.so.1) > > Mmm. I don't know what to make of that. I'd like to see a stack trace > at that point, is that possible? I'm not sure how to get a stacktrace of a process that's being run underneath valgrind, or if it's even possible. That's something I'll have to investigate. It would be quite nice... By the way, why'd you close this bug? On amd64 the bug is just as valid now as it was before... -- Kevin Brown [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
