On Do, 19 Sep 2019, Ni Va wrote:
> It's always on same machine and repeatable systematically.
So how?
> How can I launch gvim differently (with -NONE) or enable a debugger to get
> more infos ?
Compile a debug version and attach a debugger to it. Do whatever
triggers the crash and report the backtrace. I am not sure how well this
works with msys, I remember having some problems with gdb and msys
several years ago. Perhaps that changed.
On linux, you can also build an ASAN enabled version. That should give
us a hint where something went wrong.
Best,
Christian
--
Dein tägliches Quantum Sonnenschein mußt du dir täglich selbst
verdienen.
-- Hermann Sudermann
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/20190920094123.GA22701%40256bit.org.
