<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Crash on FILEOPEN with very large table feature enabled"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=138494#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Crash on FILEOPEN with very large table feature enabled"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=138494">bug 138494</a>
from <span class="vcard"><a class="email" href="mailto:ralf.habacker@freenet.de" title="Ralf Habacker <ralf.habacker@freenet.de>"> <span class="fn">Ralf Habacker</span></a>
</span></b>
<pre>(In reply to Michael Weghorn from <a href="show_bug.cgi?id=138494#c5">comment #5</a>)
<span class="quote">> Thanks. Are those steps recommended somewhere in our wiki (or elsewhere) for
> "advanced bug reporters" or so? (It's the first time I hear about this. :) )</span >
A few more details:
1. The file gdbtrace.log has been generated by following
<a href="https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace">https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace</a>
2. In the gdbtrace.log there is:
Thread 1 "soffice.bin" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51 }
#0 0x00007ffff3e4c520 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:51
#1 0x00007ffff3e4db01 in __GI_abort () at abort.c:79
#2 0x00007ffff696b430 in Scheduler::CallbackTaskScheduling() () at
/usr/lib64/libreoffice/program/libmergedlo.so
After searching for Scheduler::CallbackTaskScheduling I found
<a class="bz_bug_link
bz_status_CLOSED bz_closed"
title="CLOSED FIXED - Crash opening index dialog"
href="show_bug.cgi?id=113284">https://bugs.documentfoundation.org/show_bug.cgi?id=113284</a> where catching
exceptions is mentioned.
This is the same procedure as mentioned at
<a href="https://wiki.documentfoundation.org/Development/How_to_debug#Finding_a_stacktrace_of_an_.22ignored.22_C.2B.2B_exception">https://wiki.documentfoundation.org/Development/How_to_debug#Finding_a_stacktrace_of_an_.22ignored.22_C.2B.2B_exception</a>
for lldb.
The whole procedure then is:
(gdb) b Scheduler::CallbackTaskScheduling()
r
(gdb) set pagination off
(gdb) catch throw
Catchpoint 2 (throw)
(gdb) command 2
Type commands for breakpoint(s) 2, one per line.
End with a line saying just "end".
<span class="quote">>bt
>c
>end</span >
(gdb) set logging file /tmp/localc-crash.log
(gdb) set logging redirect on
(gdb) set logging on</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>