I'm finding most of my crashes are runtime QT problems. This stuff will let you compile just about anything, but it's delicate in the field.
I've been going through a really tedious bug hunting cycle from where I copied around a bunch of stuff and accidentally propagated some mistakes. Seems nothing to be done but to run, crash, gdb, then try to see what happened. I've observed that QT programming just seems to be like that. No help from the compiler at all as long as the types match up, and if there's a problem, it just falls on its ass unceremoniously at runtime. Is there any resource I'm missing here? Some sanity-checking anti-stupidity parser or something? Some way to get QT to generate runtime errors to give a hint what went wrong? Anonymous crashes are irritating; especially since gdb is about the most unwieldy tool since edlin. -- Michael McIntyre USDA zone 6b in SW VA, USA Silvan <[EMAIL PROTECTED]> Linux Druid ----------[ registered Linux user #243621 ]--------- http://www.geocities.com/Paris/Rue/5407/index.html ------------------------------------------------------- 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 _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
