all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Odd gdb problem
Date: Tue, 07 Dec 2021 21:33:26 +0100	[thread overview]
Message-ID: <87mtlcdujt.fsf@gnus.org> (raw)
In-Reply-To: <83r1aozim5.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 07 Dec 2021 14:48:02 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> 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?

(gdb) info break
No breakpoints or watchpoints.

> 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.

(gdb) handle SIGTRAP stop print pass
SIGTRAP is used by the debugger.
Are you sure you want to change it? (y or n) y
Signal        Stop	Print	Pass to program	Description
SIGTRAP       Yes	Yes	Yes		Trace/breakpoint trap
(gdb) run 
Starting program: /home/larsi/src/emacs/mystery/src/emacs 

Program terminated with signal SIGTRAP, Trace/breakpoint trap.
The program no longer exists.

This is with a fresh checkout.  I'm starting to think there's a bug in
the version of gdb on Debian/bookworm that the current trunk is somehow
hitting.  Perhaps I should just try to bisect the current trunk -- this
started happening this past week.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2021-12-07 20:33 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
2021-12-07 20:33       ` Lars Ingebrigtsen [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mtlcdujt.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.