From: John Wiegley <jwiegley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 22120@debbugs.gnu.org, Eric Hanchrow <eric.hanchrow@gmail.com>
Subject: bug#22120: 25.1.50; segfault while running circe
Date: Tue, 08 Dec 2015 13:03:22 -0800 [thread overview]
Message-ID: <m2wpso1wmd.fsf@newartisans.com> (raw)
In-Reply-To: <83oae0bqzi.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 08 Dec 2015 22:54:57 +0200")
>>>>> Eli Zaretskii <eliz@gnu.org> writes:
>> $7 = (struct Lisp_Cons *) 0x6c20736c69747560
>> Cannot access memory at address 0x6c20736c69747560
> That "address" is part of a string: "`utils l" (without the quotes). So I'm
> guessing some code is overwriting the stack or writing beyond the limits of
> a char array. The question is where?
Nice catch! Forgot to look for that.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2015-12-08 21:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 20:19 bug#22120: 25.1.50; segfault while running circe Eric Hanchrow
2015-12-08 20:33 ` Eli Zaretskii
2015-12-08 20:36 ` Eric Hanchrow
2015-12-08 20:54 ` Eli Zaretskii
2015-12-08 21:03 ` John Wiegley [this message]
2015-12-09 15:29 ` Eric Hanchrow
[not found] ` <83h9jrbl7b.fsf@gnu.org>
2015-12-09 19:13 ` Eric Hanchrow
2015-12-08 20:36 ` John Wiegley
2015-12-08 20:38 ` Eric Hanchrow
2015-12-10 18:42 ` bug#22120: Another backtrace Eric Hanchrow
2015-12-10 19:02 ` Eli Zaretskii
2015-12-10 19:15 ` Eric Hanchrow
2015-12-10 19:30 ` Eli Zaretskii
2015-12-12 22:37 ` Eric Hanchrow
2015-12-13 15:27 ` Eli Zaretskii
2015-12-13 17:54 ` Eric Hanchrow
2015-12-13 18:04 ` Eli Zaretskii
2015-12-13 18:07 ` Eric Hanchrow
2015-12-13 18:13 ` Eli Zaretskii
2015-12-13 18:19 ` Eric Hanchrow
2015-12-13 18:22 ` Eli Zaretskii
2015-12-13 18:29 ` Eric Hanchrow
2015-12-24 3:24 ` Eric Hanchrow
2015-12-24 16:12 ` 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=m2wpso1wmd.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=22120@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=eric.hanchrow@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).