unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Vincent Belaïche" <vincentb1@users.sourceforge.net>
Cc: 22301@debbugs.gnu.org
Subject: bug#22301: 25.1.50; Emacs crashes while lisp debugging
Date: Tue, 05 Jan 2016 18:00:31 +0200	[thread overview]
Message-ID: <83fuyc584g.fsf@gnu.org> (raw)
In-Reply-To: <84ziwkv6ki.fsf@gmail.com> (message from Vincent Belaïche on Tue, 05 Jan 2016 08:17:17 +0100)

> From: Vincent Belaïche <vincentb1@users.sourceforge.net>
> Cc: Vincent Belaïche <vincent.belaiche@gmail.com> ,
>  22301@debbugs.gnu.org
> Date: Tue, 05 Jan 2016 08:17:17 +0100
> 
> Something I had forgotten to tell you: I think that I have compiled this
> Emacs with Mingw-w64 --- well I am not 100% sure now because at some
> point of time I had problems with Minfw-64 (see
> https://sourceforge.net/p/mingw-w64/bugs/519/) and I have re-installed
> the 32 bit version (both coexist now on my machine and I select the one
> in use by editing the fstab file).
> 
> Anyway, I still don't get the debugger prompt, neither Ctrl-C (well C-Q
> C-C because I am running it from Emacs), nor F-12 do anything. However,
> if I do:
> 
>   M-x signal-process RET
>   shell RET
>   3 RET
> 
> then something happens with the debugger, I did it several times, I
> still don't get the prompt, but there is that sort of output:
> 
>   Program received signal SIGTRAP, Trace/breakpoint trap
> 
> So below, I copied the full gdb session with these. Please make me know
> whether this session is ruined or not.

You can close this session.  It cannot help us more than it already
did.  I hope we will have more information next time this happens,
using the commands I've shown.

Thanks.





  reply	other threads:[~2016-01-05 16:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-03 22:43 bug#22301: 25.1.50; Emacs crashes while lisp debugging Vincent Belaïche
2016-01-04  3:41 ` Eli Zaretskii
2016-01-04  8:00 ` Vincent Belaïche
2016-01-04 15:54   ` Eli Zaretskii
2016-01-04 22:49 ` Vincent Belaïche
2016-01-05  3:34   ` Eli Zaretskii
2016-01-05  7:17 ` Vincent Belaïche
2016-01-05 16:00   ` Eli Zaretskii [this message]
2016-01-14 16:15 ` Vincent Belaïche
2016-01-14 18:20   ` Eli Zaretskii
2016-01-14 22:54 ` Vincent Belaïche
2016-01-15  7:46   ` Eli Zaretskii
2016-01-15  7:56 ` Vincent Belaïche
2016-01-15  8:12   ` Eli Zaretskii
2016-01-19 23:34 ` Vincent Belaïche
2016-01-20  1:58   ` Alexis
2016-01-20  4:31   ` Eli Zaretskii
2016-01-20  8:50 ` Vincent Belaïche
2016-01-20  9:49   ` Eli Zaretskii
2016-01-20 15:30   ` Nicolas Richard
2016-02-01  9:18 ` Vincent Belaïche
2016-02-01 17:22 ` Vincent Belaïche
2016-02-02  7:14 ` Vincent Belaïche
2016-12-07 18:55   ` Glenn Morris

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=83fuyc584g.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22301@debbugs.gnu.org \
    --cc=vincentb1@users.sourceforge.net \
    /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).