[Libreoffice] Illegal operations in connectivity::OSQLParseNode::impl_parseNodeToString_throw

Michael Meeks michael.meeks at novell.com
Tue May 24 02:43:54 PDT 2011

Hi Alex,

On Mon, 2011-05-23 at 18:42 +0200, Alexander Thurgood wrote:
> While attempting to profile a systematic crash on Mac OSX :
> https://bugs.freedesktop.org/show_bug.cgi?id=37487
> I see this in the output of the assembly language instructions :

	Hmm :-) it seems unlikely that there are truly invalid instructions
generated by the compiler [ although compiler bugs are not unknown ],
and more likely that the profiling tool is incomplete (to me at least).

> I have no idea how or if these are handled, presumably by SIGILL ?

	They would cause a nice shutdown/crash sequence I guess, but I doubt
this is the problem.

	One thing you can do that would be incredibly useful, is to get
valgrind running on the mac: this might help:


	For a large set of memory corruption crashers, (and even invalid
instructions if they exist), valgrind provides a fantastic debugging
harness that can see corruptions at source - way before they cause odd
effects (sometimes much later).

	Any chance of giving that a spin ? [ we would need the log ].



 michael.meeks at novell.com  <><, Pseudo Engineer, itinerant idiot

More information about the LibreOffice mailing list