2011/3/30 ValentÃn <[email protected]> > Hi! > > I'm trying to familiarize myself with Shotwell code and I think that > it could be great if I could debug it to see what are the program > doing during it's execution. And I don't know why, but I can't. > > Learning Vala I've read that I could debug Vala programs with gdb (or > Nemiver, which I prefer) and I've done it with my little testing > programs. Compiling with valac with -g option allows me to see Vala > code at debugging --and also some C code where there are not exactly > matches between Vala and C. This is that I've read: > http://live.gnome.org/Vala/Tutorial#Debugging > > But with Shotwell I can't do that. I've seen at the makefile and it > seems to have the -g option by default, so I don't know where is the > problem. > > So, what do you do yo debug Shotwell? Do you read the C code directly? > I'm happy with C, but the Vala-generated C is a bit weird and > difficult to read... >
Valentin, in the world of new programming languages (i.e. Vala) things are a little bit rough sometimes. :) With Vala 0.10.x, the Vala compiler generates #line statements in the generated C code. That lets GDB understand the correspondence between Vala source lines and C source lines, and so when you debug (either in GDB directly, or in a graphical debugger like Nemiver) you see Vala code. Unfortunately Vala 0.11.x does not yet generate #line directives: https://bugzilla.gnome.org/show_bug.cgi?id=635095 That means that when debugging code built with Vala 0.11, you only get to see C code at the moment. Yes, that's pretty inconvenient. I hope the Vala team will fix this in time for the Vala 0.12 release. > > Any other way to familiarize myself with the program? Do you have any > guide or something? > You want to read this: http://trac.yorba.org/wiki/ShotwellArchitectureOverview adam _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
