You can sometimes get a more useful error using gdb.. Simplest way is to start Nuke, then run:
gdb -p 1234 ..where 1234 is the nuke process id. Then when you get the "(gdb) " prompt, type continue and wait for Nuke to crash When it dies, type "bt" (or "backtrace") and it might give you the name of the node that is dying... or... a bunch of unhelpful "????" lines On 06/10/11 03:40, Dorian Fevrier wrote: > Hi all! > > We have nuke crashing without any messages, nothing... I'm currently > trying to know where this happen and, it happen (of course...) within the: > > nuke.execute( writeNode, f, f, 1, forcedViews ) > > I would like to know what are nodes that could do Nuke crash. So I would > like to know what are nodes running during Nuke crash (doesn't seems to > be a memory prob). > > I know this is not something easy to follow with multithreading but > something like: > > node1 -> Start > node2 -> Start > node3 -> Start > node2 -> End > node4 -> Start > node1 -> End > node3 -> End > > Could be really enought for me. To find the part where nuke crash. > > Is there a way to script during a evaluation start and end to print the > node name? > > How deal with this kind of prob? > > Thank in advance. > > Have a good day! > _______________________________________________ > Nuke-python mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python -- ben dickson 2D TD | [email protected] rising sun pictures | www.rsp.com.au _______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
