Re: igc: trying to chase a crash

[Eli Zaretskii <eliz@gnu.org>]

> From: Óscar Fuentes <ofv@wanadoo.es>
> Date: Mon, 25 Nov 2024 20:53:03 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > SIGSEGV is used by MPS to implement memory barriers.  The file
> > src/.gdbinit on the branch has this:
> >
> >   # Pass on signals used by MPS to suspend threads.
> >   if defined_HAVE_MPS
> >     # Print SIGSEGV for now, since it makes the logs more useful.  Don't
> >     # stop, though.
> >     handle SIGSEGV nostop print pass
> >     handle SIGXFSZ nostop noprint pass
> >     handle SIGXCPU nostop noprint pass
> >   end
> 
> So does it make sense to run igc under gdb for obtaining backtraces when
> it crashes?

Yes, it does.  Because if you hit a real segfault, it will stop again.

> 
> >>   389 |       if (record && BUF_MARKERS (b))
> >>       |           ~~~~~~ ^~
> >>       |           |
> >>       |           int
> >
> > I tried to fix this now, please try again.
> 
> Thanks. That instance compiles now, but then...
> 
> ../../emacs/src/fns.c: In function ‘weak_hash_remove_from_table’:
> ../../emacs/src/fns.c:5789:26: error: invalid operands to binary == (have ‘Lisp_Object’ and ‘Lisp_Object’)
>  5789 |               && hashval == WEAK_HASH_HASH (h, i)
>       |                          ^~ ~~~~~~~~~~~~~~~~~~~~~
>       |                             |
>       |                             Lisp_Object

Fixed.

How about if you say "make -k", so that we see all the problems at
once, not one by one?