Have you tried running the code using Valgrind's memcheck and Helgrind?
It might reveal something was was hidden before.
Were you linking with the same libraries for 6.2v4?
Wouter
On 13/09/2011 11:34, Anders Langlands wrote:
Hi, I'm getting a segfault in tls_destructor when running a plugin in
nuke 6.3v1:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x4d5c9940 (LWP 24833)]
0x000000000120236a in tls_destructor ()
(gdb) bt
#0 0x000000000120236a in tls_destructor ()
#1 0x00000000012024d4 in thread_proxy ()
#2 0x0000003181e0673d in start_thread () from /lib64/libpthread.so.0
#3 0x00000031812d3f6d in clone () from /lib64/libc.so.6
The exact same code works just fine in 6.2v4. Can anybody think what
might be going wrong here? I don't really know how to start looking. I'm
linking against OpenEXR 1.7 and boost 1.43 (using asio and consequently
thread). My gut tells me it's boost::asio that's not playing well here,
but I can't really lose it since it does most of the hard work, and I'm
not really sure how to go about finding the exact source of the problem.
Any ideas?
Cheers,
Anders
_______________________________________________
Nuke-dev mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
--
Wouter Klouwen, Software Engineer
The Foundry, 1 Wardour Street, London, W1D 6PA, UK
Tel: +442074340449 • Fax: +442074341550 • thefoundry.co.uk
The Foundry Visionmongers Ltd • Reg.d in England and Wales No: 4642027
_______________________________________________
Nuke-dev mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
