[Libreoffice-bugs] [Bug 138494] Crash on FILEOPEN with very large table feature enabled

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=138494

--- Comment #8 from Ralf Habacker <ralf.habacker at freenet.de> ---
(In reply to Michael Weghorn from comment #5)
> 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. :) )

A few more details:

1. The file gdbtrace.log has been generated by following
https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace

2. In the gdbtrace.log there is: 

Thread 1 "soffice.bin" received signal SIGABRT, Aborted.
__GI_raise (sig=sig at entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51      }
#0  0x00007ffff3e4c520 in __GI_raise (sig=sig at 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
https://bugs.documentfoundation.org/show_bug.cgi?id=113284 where catching
exceptions is mentioned. 

This is the same procedure as mentioned at
https://wiki.documentfoundation.org/Development/How_to_debug#Finding_a_stacktrace_of_an_.22ignored.22_C.2B.2B_exception
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".
>bt
>c
>end
(gdb) set logging file /tmp/localc-crash.log
(gdb) set logging redirect on
(gdb)  set logging on

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20201126/9ab4656d/attachment.htm>