From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Odd gdb problem
Date: Tue, 07 Dec 2021 14:48:02 +0200 [thread overview]
Message-ID: <83r1aozim5.fsf@gnu.org> (raw)
In-Reply-To: <87lf0xjyl9.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 06 Dec 2021 20:57:22 +0100)
> 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.
next prev parent reply other threads:[~2021-12-07 12:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 19:43 Odd gdb problem Lars Ingebrigtsen
2021-12-06 19:55 ` Eli Zaretskii
2021-12-06 19:57 ` Lars Ingebrigtsen
2021-12-07 12:48 ` Eli Zaretskii [this message]
2021-12-07 20:33 ` Lars Ingebrigtsen
2021-12-08 0:22 ` Lars Ingebrigtsen
2021-12-08 0:29 ` Lars Ingebrigtsen
2021-12-08 8:13 ` Andreas Schwab
2021-12-08 8:16 ` Lars Ingebrigtsen
2021-12-08 8:34 ` Lars Ingebrigtsen
2021-12-08 8:50 ` Andreas Schwab
2021-12-09 1:10 ` Lars Ingebrigtsen
2021-12-12 11:08 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r1aozim5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).