all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Vincent Belaïche" <vincent.b.1@hotmail.fr>
To: 18516@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Cc: "Vincent Belaïche" <vincent.b.1@hotmail.fr>
Subject: bug#18516: Acknowledgement (24.4.50; EMACS crashes when I try to open Elisp manual)
Date: Sun, 21 Sep 2014 23:13:33 +0200	[thread overview]
Message-ID: <80k34wfzia.fsf@gmail.com> (raw)
In-Reply-To: <80k34xgxnv.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]

Dear Eli et alii,

Sorry for my previous email, actually I had done a mistake when trying
to launch from gdb as I had provided to `run' the slash the absence of
which is needed for crashing, that is why there was no crash with gdb!
Sorry for loosing your precious time... :-/

So, actually, I *can* make it crash under gdb.

The problem is that there is not much information provided by gdb --- no
more information than if there is no crash --- if I type:

(gdb) bt full

I get:

(gdb) No stack.

whether it is before run, after it (crash done), or before or after
clicking on the "Ne pas envoyer" (=Don't send) button of the MSW crash
popup windown.

and `bt full' does not seem to have any other effect.

and if I type

(gdb) xbacktrace

Then I get:

(gdb) Undefined command: "xbacktrace".  Try "help".

I have gdb 7.4 (maybe there are more recent ones for MSWindows XP)

What I see when the crash occurs is the usual MSWindows crash popup that
propose you to send a file that contains a dump of your memory ---
possibly containing confidential data from other applications, this is
why I never accept to do such a thing and use as much as possible free
S/W.

  Vincent.

PS: attached is a screenshot of after the crash (I only moved the
3 windows (1= gdb in console, 2=Emacs, 3=MSW crash popup) for all of
them to be visible.


[-- Attachment #2: Sans titre.PNG --]
[-- Type: image/png, Size: 102921 bytes --]

  parent reply	other threads:[~2014-09-21 21:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-21  8:55 bug#18516: 24.4.50; EMACS crashes when I try to open Elisp manual Vincent Belaïche
2014-09-21 11:50 ` bug#18516: Acknowledgement (24.4.50; EMACS crashes when I try to open Elisp manual) Vincent Belaïche
2014-09-21 15:59   ` bug#18516: 24.4.50; EMACS crashes when I try to open Elisp manual Eli Zaretskii
2014-09-21 16:00 ` Eli Zaretskii
2014-09-21 17:09 ` bug#18516: Acknowledgement (24.4.50; EMACS crashes when I try to open Elisp manual) Vincent Belaïche
2014-09-21 17:28   ` Eli Zaretskii
2014-09-21 18:00 ` Vincent Belaïche
2014-09-21 18:09   ` Eli Zaretskii
2014-09-21 21:13 ` Vincent Belaïche [this message]
2014-09-22  2:49   ` Eli Zaretskii
2014-09-22  4:21 ` Vincent Belaïche
2014-09-22  6:21   ` Dmitry Antipov
2014-09-22 14:39     ` Eli Zaretskii
2014-09-22  4:26 ` Vincent Belaïche
2014-09-22 17:13 ` Vincent Belaïche
2014-09-22 17:53   ` Eli Zaretskii
2014-09-23  9:51 ` Vincent Belaïche

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=80k34wfzia.fsf@gmail.com \
    --to=vincent.b.1@hotmail.fr \
    --cc=18516@debbugs.gnu.org \
    --cc=eliz@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.