https://bugs.documentfoundation.org/show_bug.cgi?id=106294
LeMoyne Castle <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|[email protected] |[email protected]
|desktop.org |
--- Comment #4 from LeMoyne Castle <[email protected]> ---
@Aron - that is a very good question ... There are other ways to start Basic
besides the way that was protected by Caolan under bug 88985.
There are two issues here: see the longer (longest?) note on bug 107297.
The upshot:
I will work on the separate issues uncovered by 'crash in Basic on close of LO'
bugs in the following way and order:
1. Bug 106294 - establish consistent protection for Basic at ALL calls that
start StarBasic as Caolan did for bug 88985. External to Basic + a direct fix.
Can test directly with close during long-running macro.
2. Bug 107297 - Make Basic's destructors public to bring the destruction of
Basic objects in compliance with C++ standards/best practices in order to avoid
compiler+linker confusion and gross differences between VS and gcc versions.
Internal to Basic - an indirect (compiler-mediated) potential(!) fix. Might be
hard to verify and will require much more thorough testing of Basic to try to
avoid side effects. Will be obvious as a separate issue if the protection fix
only works reliably on Linux and we still get crashes on Windows.
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
