Re: MPS: Loaded pdump

[Eli Zaretskii <eliz@gnu.org>]

> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: Helmut Eller <eller.helmut@gmail.com>,  emacs-devel@gnu.org
> Date: Thu, 16 May 2024 14:21:20 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > and the object A in the PSEUDOVECTORP call cannot be looked at:
> >
> >   (gdb) p a
> >   $2 = XIL(0xb93100d)
> >   (gdb) xtype
> >   Lisp_Vectorlike
> >   Cannot access memory at address 0xb931008
> 
> Usually calling igc_postmortem helps in such a case.

Compliance!

  Thread 1 received signal SIGSEGV, Segmentation fault.
  PSEUDOVECTORP (code=13, a=0xb95c2dd) at lisp.h:755
  755       return lisp_h_XLP (o);
  (gdb) call igc_postmortem()
  (gdb) c
  Continuing.

  Thread 1 received signal SIGSEGV, Segmentation fault.
  PSEUDOVECTORP (code=13, a=0xb95c2dd) at lisp.h:755
  755       return lisp_h_XLP (o);
  (gdb) call igc_postmortem()

  traceanc.c:611: Emacs fatal error: assertion failed: !RingIsSingle(_old)
  [Thread 28004.0x5c2c exited with code 0]

  Thread 1 received signal SIGTRAP, Trace/breakpoint trap.
  0x76d258d3 in KERNELBASE!DebugBreak () from C:\WINDOWS\SysWOW64\KernelBase.dll
  The program being debugged was signaled while in a function called from GDB.
  GDB remains in the frame where the signal was received.
  To change this behavior use "set unwindonsignal on".
  Evaluation of the expression containing the function
  (igc_postmortem) will be abandoned.
  When the function is done executing, GDB will silently stop.

Now what?