From: Philippe W. <phi...@sk...> - 2018-02-07 21:31:54
|
On Wed, 2018-02-07 at 15:25 -0600, Adam Scott wrote: > Even with the patches from that bug the error still occurred. Ouch. Bad luck. As I understand from the stack trace, the valgrind crash happens somewhere inside google breakpad, which is itself a crash reporter ? If this is correct, it might be worth trying to see what is the reason of the crash reporter starting up ? And maybe you could disable this crash reporter ? (otherwise, it would be useful to add some info in the bug report references, with the details of your crash, just in case someone looks further on these clone handling limitations. Philippe |