Re: terminate called after throwing an instance of 'boost::python::error_already_set
> On 27 May 2022, at 21:17, Larry Martell wrote: > > I have a script that has literally been running for 10 years. > Suddenly, for some runs it crashes with the error: > > terminate called after throwing an instance of > 'boost::python::error_already_set This is from an extension that is written in C++ that raised a C++exception, not a python one. The default action in C++ is to terminal the process so python does not get a chance to prints its stack. > > No stack trace. Anyone have any thoughts on what could cause this > and/or how I can track it down? You will need to use a C++ level debugger to see which extension is crashing. gdb on linux, lldb on macOs or visual studio on windows. Barry > -- > https://mail.python.org/mailman/listinfo/python-list > -- https://mail.python.org/mailman/listinfo/python-list
Re: terminate called after throwing an instance of 'boost::python::error_already_set
On 28/05/2022 11.11, Larry Martell wrote: > > > On Fri, May 27, 2022 at 5:51 PM dn <mailto:pythonl...@danceswithmice.info>> wrote: > > On 28/05/2022 08.14, Larry Martell wrote: > > I have a script that has literally been running for 10 years. > > Suddenly, for some runs it crashes with the error: > > > > terminate called after throwing an instance of > 'boost::python::error_already_set > > > > No stack trace. Anyone have any thoughts on what could cause this > > and/or how I can track it down? > > 1 a change to Python interpreter being used > > 2 a change to the boost library being used > > 3 a change to lower levels in 'the s/w stack' or h/w > > 4 a change to the data being passed-across > > > Definitely not 1. 4 is always the case - every run is with different > data. 2 and 3 I don’t know. What is boost and how does Python use it? > None of my code is importing it. How can get a stack trace when it > crashes with just that message? A possibly/hopefully helpful explanation appears at: https://misspent.wordpress.com/2009/10/11/boost-python-and-handling-python-exceptions/ -- Regards, =dn -- https://mail.python.org/mailman/listinfo/python-list
Re: terminate called after throwing an instance of 'boost::python::error_already_set
On Fri, May 27, 2022 at 5:51 PM dn wrote: > On 28/05/2022 08.14, Larry Martell wrote: > > I have a script that has literally been running for 10 years. > > Suddenly, for some runs it crashes with the error: > > > > terminate called after throwing an instance of > 'boost::python::error_already_set > > > > No stack trace. Anyone have any thoughts on what could cause this > > and/or how I can track it down? > > 1 a change to Python interpreter being used > > 2 a change to the boost library being used > > 3 a change to lower levels in 'the s/w stack' or h/w > > 4 a change to the data being passed-across Definitely not 1. 4 is always the case - every run is with different data. 2 and 3 I don’t know. What is boost and how does Python use it? None of my code is importing it. How can get a stack trace when it crashes with just that message? > -- https://mail.python.org/mailman/listinfo/python-list
Re: terminate called after throwing an instance of 'boost::python::error_already_set
On 28/05/2022 08.14, Larry Martell wrote: > I have a script that has literally been running for 10 years. > Suddenly, for some runs it crashes with the error: > > terminate called after throwing an instance of > 'boost::python::error_already_set > > No stack trace. Anyone have any thoughts on what could cause this > and/or how I can track it down? 1 a change to Python interpreter being used 2 a change to the boost library being used 3 a change to lower levels in 'the s/w stack' or h/w 4 a change to the data being passed-across -- Regards, =dn -- https://mail.python.org/mailman/listinfo/python-list
terminate called after throwing an instance of 'boost::python::error_already_set
I have a script that has literally been running for 10 years. Suddenly, for some runs it crashes with the error: terminate called after throwing an instance of 'boost::python::error_already_set No stack trace. Anyone have any thoughts on what could cause this and/or how I can track it down? -- https://mail.python.org/mailman/listinfo/python-list
