Hi Elias, from the Assert'ions point of view it looks as if you are trying to index an empty UCS_string in FnCommand::run_command(). I would recommend to check the size() of each UCS_string created in FnCommand::run_command(). I am have seen problems with the Backtrace feature from time to time, giving not reproducible stack traces every now and then. So it might be that first the assertion fails and then, when displaying the call stack for the assertion, __cxa_de results shall be freed() but doing to segfaults from time to time. /// Jürgen On 01/17/2017 08:48 PM, Elias Mårtenson
wrote:
|
- [Bug-apl] Crash with stack trace Elias Mårtenson
- Re: [Bug-apl] Crash with stack trace Juergen Sauermann
- Re: [Bug-apl] Crash with stack trace Elias Mårtenson
- Re: [Bug-apl] Crash with stack trace Juergen Sauermann
- Re: [Bug-apl] Crash with stack trace Elias Mårtenson