Re: Odd gdb problem

[Eli Zaretskii]

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Mon, 06 Dec 2021 20:57:22 +0100
> Cc: emacs-devel@gnu.org
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Is this with or without native-comp?
> 
> Without any configure options.
> 
> > Did you try rebuilding Emacs (i.e. delete temacs and bootstrap-emacs,
> > and say "make")?
> 
> Yup; did a "make extraclean" first.

SIGTRAP is normally the signal generated when the program hits a
breakpoint, so this is strange: it looks like GDB received a spurious
SIGTRAP that it couldn't associate with one of its breakpoints.  What
does "info break" say inside GDB?

One other idea I have is to say

  (gdb) handle SIGTRAP stop print pass

and see what happens then.  Maybe you will be able to see where does
this SIGTRAP originate from.