Here it comes: 0x0000000803e9bbe2 in g_ascii_strcasecmp () from /usr/local/lib/libglib-2.0.so.0 (gdb) bt #0 0x0000000803e9bbe2 in g_ascii_strcasecmp () from /usr/local/lib/libglib-2.0.so.0 #1 0x0000000803eb0012 in g_parse_debug_string () from /usr/local/lib/libglib-2.0.so.0 #2 0x00000008006a8ed1 in rs_debug_setup () from /usr/local/lib/librawstudio-2.0RC2.so.0 #3 0x0000000000417224 in main ()
very funny. So that's why -d debug helped, right? One more data point, possibly unrelated: starting with -d performance rawstudio reports 1 cpu core, on a machine wich reports: CPU: AMD Phenom(tm) II N930 Quad-Core Processor (1995.02-MHz K8-class CPU) FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0: <ACPI CPU> on acpi0 cpu1: <ACPI CPU> on acpi0 cpu2: <ACPI CPU> on acpi0 cpu3: <ACPI CPU> on acpi0 seems fishy. Am Mittwoch, den 06.04.2011, 15:00 +0200 schrieb Klaus Post: > Hi! > > Could you possibly get a longer backtrace, so we can see where the > call is originating from? > > I don't know if you can do the same as Ubuntu with "gdb rawstudio" and > enter 'r'<enter> to start Rawstudio, and 'bt'<enter> when you > experience the crash? > > > If I didn't say so before: I think the teams concentration on image > quality and lean workflow make rawstudio a joy to work with. > The best > raw converter in many ways. Thank you! > I just discovered I now can use my 2nd monitor. Yay! Great! > that > _really_ helps! > > Cheers, Mathias > Thanks - it seems like we are close! > > Regards, Klaus Post > > http://www.klauspost.com > > > _______________________________________________ > Rawstudio-users mailing list > [email protected] > http://rawstudio.org/cgi-bin/mailman/listinfo/rawstudio-users _______________________________________________ Rawstudio-users mailing list [email protected] http://rawstudio.org/cgi-bin/mailman/listinfo/rawstudio-users
