Hi Thomas, Thanks for getting back to me.
It seems we have reached an interesting situation. After reconfiguring (with --enable-debug), reinstalling, executing gdb and seeding using 'run' with the same params, I can not reproduce the segfault no matter how many threads I throw at it, even all the way up to 64. However, outside of gdb I get the segfault as always. Perhaps we have some sort of race condition or timing issue. Some googling shows that this is not entirely uncommon. Some others in the same boat have suggested running with Valgrind. (http://stackoverflow.com/questions/7057651/cannot-reproduce-segfault-in-gdb) Could you please advise on the next step? Would the core dump be useful? Best, Matt -- View this message in context: http://osgeo-org.1560.n6.nabble.com/mapcache-seed-segfault-when-using-threading-SEC-UNCLASSIFIED-tp5007582p5010188.html Sent from the Mapserver - User mailing list archive at Nabble.com. _______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
