I haven't tried it yet, but this gdb feature for fedora 13 looks like it would be able to give you a sensible python stack trace: https://fedoraproject.org/wiki/Features/EasierPythonDebugging
On Thu, May 13, 2010 at 1:54 PM, Paul Molodowitch <[email protected]>wrote: > Hey - I'm having to deal with solving some intermittent hard crashes in > Maya 2011, and noticed that it now prints out a c / assembly style > stack-trace, and a memory dump. > > I think some of this may always been saved away somewhere, but now that > it's in my face, it got me thinking... has anyone ever been able to make any > use of this information, particularly in a python-ish context? Ie, been > able to pull any useful information out of it, such as what python call it > was in when it crashed? Or even what maya command it may have been running? > > I can always fall back on spamming a bunch of print statements to nail down > where the crash is occurring, but this can be a bit of a pain when (as in > this case) the crash isn't happening reliably... > > Any thoughts / tips people may have had when dealing with similar problems > would be useful! > > - Paul > > -- > http://groups.google.com/group/python_inside_maya -- http://groups.google.com/group/python_inside_maya
