Since I mentioned my problems with trying to start debugging a debug build of hugin, I'll describe the partial answer I've found so far. Maybe anyone else who would try to debug hugin would already know this stuff. But in case that is not true:
I think CodeBlocks was failing because the underlying gdb was unresponsive (haven't verified yet by retrying with CodeBlocks). Using gdb directy, it was unresponsive after displaying a line starting with [ and ending with ] and otherwise blank. After trying other things, I eventually realized the meaning was failure to get a response from some server that it was trying to download debug info from. Aborting the hung gdb and restarting, it used a cache for all the debug symbols it had gotten the first time (before the failure) and got an immediate response from the server that had failed the first time and got through a bunch more before failing again. Third time it finished downloading all those symbols. Now I'm figuring out basics of using gdb (identifying the correct one of hugin's 36 threads to get a meaningful backtrace, setting breakpoints, looking at things). -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/13414418-5c36-494b-b8e6-2cf586daed3an%40googlegroups.com.
