Gvim 8.1 32bits crash on winOS 7 64bits

[Ni Va]

Hi,

Here is an output of gvim crash on windows seven 64bits.

Gvim 8.1 is build under MSYS with Make_ming.mak with 1-2056 patches.

Signature du problème :

  Nom d’événement de problème: APPCRASH

  Nom de l’application: gvim.exe

  Version de l’application: 8.1.282.0

  Horodatage de l’application: 5d837373

  Nom du module par défaut: vm3dum.dll

  Version du module par défaut: 7.14.1.51

  Horodateur du module par défaut: 4e33522a

  Code de l’exception: c0000005

  Décalage de l’exception: 000199ab

  Version du système: 6.1.7601.2.1.0.256.48

  Identificateur de paramètres régionaux: 1036

  Information supplémentaire n° 1: 0a9e

  Information supplémentaire n° 2: 0a9e372d3b4ad19135b953a78882e789

  Information supplémentaire n° 3: 0a9e

  Information supplémentaire n° 4: 0a9e372d3b4ad19135b953a78882e789

Lire notre déclaration de confidentialité en ligne :  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x040c

Si la déclaration de confidentialité en ligne n’est pas disponible, lisez la version hors connexion : C:\Windows\system32\fr-FR\erofflps.txt

[Christian Brabandt]

Can you reproduce the crash?

--
--
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 vim_dev+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/28ab1f69-79a1-4cb3-9c42-9c8cee394866%40googlegroups.com.

[Ni Va]

It's always on same machine and repeatable systematically. 

How can I launch gvim differently (with -NONE) or enable a debugger to get more infos ?

To unsubscribe from this group and stop receiving emails from it, send an email to vim...@googlegroups.com.

[Christian Brabandt]

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