From: Eli Zaretskii <eliz@gnu.org>
To: vincent.belaiche@gmail.com (Vincent Belaïche)
Cc: 23704@debbugs.gnu.org
Subject: bug#23704: 25.1.50; Emacs crash in syntax.c
Date: Mon, 06 Jun 2016 21:45:54 +0300 [thread overview]
Message-ID: <834m96tau5.fsf@gnu.org> (raw)
In-Reply-To: <84k2i2fg6d.fsf@gmail.com> (vincent.belaiche@gmail.com)
> From: vincent.belaiche@gmail.com (Vincent Belaïche)
> Cc: Vincent Belaïche <vincent.belaiche@gmail.com>
> Date: Mon, 06 Jun 2016 18:14:18 +0200
>
> (gdb) p PT_ADDR
> $1 = (unsigned char *) 0x521073e " long as we don't have any longer the \\NEWLINE the problem is solved. So it could be:\n\n\n\n--8<----8<----8<----8<----8<-- begin -->8---->8---->8---->8---->8----\n in_input_funnies=`echo \"$in_input\" \\\n "...
> (gdb) p GPT_ADDR
> $2 = (unsigned char *) 0x5210677 ""
> (gdb) p GPT
> $3 = 1651
Not exactly what I expected, which might mean my theory about the
crash reasons is incorrect (although the code is still unsafe).
Hmm...
> The PT_ADDR seems to be pointing at the content of an email that I was
> editing when the crash occurred --- fortunately nothing confidential
> -)), some discussion in Texinfo bug mailing list, concerning support for
> spaces in filenames. If you are interested the thread is titled:
>
> REVIEW REQUEST - user manual generation
>
> I have also attached a screen capture of crashed Emacs, that may help
> you see what the content of the edited buffer was when the crash
> occurred. It seems that the crash occurred while I was editing the
> sentence « So it could be: ... ».
PT_ADDR is the address of point in buffer text, so you were editing
the sentence where it points, i.e. the sentence before that.
next prev parent reply other threads:[~2016-06-06 18:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 5:25 bug#23704: 25.1.50; Emacs crash in syntax.c Vincent Belaïche
2016-06-06 7:36 ` Andreas Schwab
2016-06-06 14:52 ` Eli Zaretskii
2016-06-06 15:03 ` Andreas Schwab
2016-06-06 14:49 ` Eli Zaretskii
2016-06-06 16:14 ` Vincent Belaïche
2016-06-06 18:45 ` Eli Zaretskii [this message]
2016-06-06 17:17 ` Paul Eggert
2016-06-06 18:58 ` Eli Zaretskii
2016-06-06 20:07 ` Paul Eggert
2016-06-07 2:38 ` Eli Zaretskii
2016-06-07 7:26 ` Paul Eggert
2016-06-07 15:52 ` Eli Zaretskii
2016-06-07 16:36 ` Paul Eggert
2016-06-07 17:17 ` Eli Zaretskii
2016-06-07 21:46 ` Vincent Belaïche
2016-06-07 22:11 ` Paul Eggert
2016-06-08 5:34 ` Vincent Belaïche
2016-06-08 16:41 ` Eli Zaretskii
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=834m96tau5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23704@debbugs.gnu.org \
--cc=vincent.belaiche@gmail.com \
/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).