<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Some forms stall with 100% on open - It's a date field problem"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=110997#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Some forms stall with 100% on open - It's a date field problem"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=110997">bug 110997</a>
from <span class="vcard"><a class="email" href="mailto:lionel@mamane.lu" title="Lionel Elie Mamane <lionel@mamane.lu>"> <span class="fn">Lionel Elie Mamane</span></a>
</span></b>
<pre>(In reply to Alex Thurgood from <a href="show_bug.cgi?id=110997#c5">comment #5</a>)
<span class="quote">> On my master debug-enabled build, attempting to open the form in a lldb
> session shows this:</span >
<span class="quote">> Process 1237 stopped
> * thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGSEGV</span >
<span class="quote">> Continuing in the session allows the form to be displayed.</span >
<span class="quote">> Attaching bt from sigsegv and further session output.</span >
Alex, when Java is used, some SIGSEGVs are "normal", as in they are used
internally by Java, caught and treated by Java. So, when Java is being used,
any SIGSEGV that does not actually crash/abort LibreOffice (meaning it was
treated by Java) should be ignored.
Unless you are diagnosing a crash/abort caused by a SIGSEGV, I recommend to
setup lldb to ignore SIGSEGVs altogether. Not sure how to do it in lldb, but in
gdb the command is "handle SIGSEGV noprint nostop pass".</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>