https://bugs.documentfoundation.org/show_bug.cgi?id=104952
--- Comment #25 from Kiss-Kálmán Dániel <kisskalmandan...@gmail.com> ---
(In reply to Aron Budea from comment #24)
> Dániel, care to try bibisecting the bug to help find the commit that caused
> this issue? (basic info on bibisecting: [1] and [2])
>
> You need git (from Cygwin for example) and bibisect-win32-5.3 git repository
> from [3]. I know it sounds alien, but it can help pinpoint the exact commit
> responsible for the crash (a backtrace would still be helpful additionally).
>
> [1] https://wiki.documentfoundation.org/QA/Bibisect
> [2] https://wiki.documentfoundation.org/QA/Bibisect/Windows
> [3]
> https://wiki.documentfoundation.org/QA/Bibisect/Windows#bibisect-win32-5.3
Hi Aron, pls help.
So I have to download the bibisec source of LO. It is special kinda LO to find
bugs (normal LO is not good for that). I need to build/compile an LO. I need to
start that spec LO (swriter) & procdump to catch the crash. It creates a dump
file (automatically when crash happens?), and I have to windbg somehow that
dump file. Am I right?
Waiting for your answer,
an alien from planet Win10 ;)
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
