On Thu, 2012-05-31 at 12:28 -0400, Jerry Feldman wrote:
So it does appear that libz is threadsafe. I have not worked on threads in a while. I always assume library functions are not threadsafe unless I learn otherwise. Could possibly be that the GPS code has a bug. At this point I am just guessing not knowing your app. One of the real beauties of Purify <http://www-01.ibm.com/software/awdtools/purify/unix/> is that it is able to find a lot of issues that other debugging options miss. The type of issues you are having are perfect for purify. While the product is pricery, you could use the trial version. A few years ago, when I was at Compaq, a guy at one of our meetings described a problem with his software. He had used other tools, but none found his problem. At my suggestion he tried Purify, it found the problem very quickly and his company decided to pay for a license.
Very strange. In purify, my application stops with a segmentation violation before it starts. That is, the program loaed seems to be loading a library (libkakadu which is a very fast JPEG2000 decoder). It is still in the startup code. The entry point in the library is _init (if I understand what purify is telling). My main() has not been called. Hard to debug a program when you never get a chance to start... Maybe it is because I am not running a supported kernel. No openSUSE kernels are supported by purify. I think I will see what ElectricFence tells. Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse-programming+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-programming+owner@opensuse.org