https://bugs.documentfoundation.org/show_bug.cgi?id=125516
--- Comment #18 from Julien Nabet <[email protected]> ---
(In reply to V Stuart Foote from comment #17)
> (In reply to Julien Nabet from comment #16)
> > V Stuart: do you think it could be possible you build sources by following
> > https://wiki.documentfoundation.org/Development/BuildingOnWindows (with
> > enable-dbgutil in autogen.input) to add some manual traces in order to debug
> > this?
> ...
> Always assumed the only thing I can't do is add additional asserts or
> break-points. Would my WinDbg backtraces for an issue improve much beyond
> attachment 155199 [details] or attachment 155200 [details] if I figure out
> how to clone the git and link to source?
I'll be honest, it's far more cumbersome to build on Windows than on Linux.
When installing all prerequisites, you can see building has been thought above
all for Linux users (I won't complain, I use Linux at home :-)).
However, it's simpler than some years ago when I had given up.
The things I don't like:
- windbg: you find far less doc to debug than for gdb, putting a break at a
specific line isn't intuitive, values of vars are often pointer values not
useful values, !analyze -v provide less info than gdb's "bt", etc.
- build fail after some updates so sometimes you must type "make <some
module>.clean". You don't need to do this on Linux or very rarely!
and when you don't know which module fail, you must build from scratch with
"make clean && make"
Anyway, the advantage is you can add logs by putting std::cerr << "<messages>
\n"; (with #include <iostream>) and display values of vars, you can test some
patches proposed by devs, you can disable some blocks, etc.
Now if you're not a programmer, perhaps it won't worth it for you. You decide!
:-)
--
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
