unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jim Meyering <jim@meyering.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 14264@debbugs.gnu.org
Subject: bug#14264: 24.3.50; SEGV in char_table_ref's use of SUB_CHAR_TABLE_P
Date: Sat, 27 Apr 2013 01:44:27 +0200	[thread overview]
Message-ID: <87bo90zwkk.fsf@rho.meyering.net> (raw)
In-Reply-To: <8361zavb12.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 25 Apr 2013 19:18:49 +0300")

Eli Zaretskii wrote:

>> From: Jim Meyering <jim@meyering.net>
>> Date: Thu, 25 Apr 2013 07:57:13 +0200
>>
>> I suspect that I would have a hard time reproducing this failure
>> starting from emacs -Q (too many moving pieces in my .emacs and .gnus.el).
>>
>> I noticed this when running a version of emacs built from
>> git of at least a few days ago, and reproduced it again
>> using the latest from this evening:
>>
>>     8b8d4a3a0c4de5d65a4d13163542c7776f3b3913
>>     Author: Stefan Monnier <monnier@iro.umontreal.ca>
>>     Date:   Wed Apr 24 23:25:34 2013 -0400
>>
>>     * lisp/progmodes/octave-mod.el (octave-smie-forward-token): Only emit
>>     ...
>>
>> Reading mail with GNUS, this segmentation fault strikes when I attempt
>> to read the following message from a local nnml folder:
>> http://thread.gmane.org/gmane.comp.gnu.coreutils.bugs/26038/focus=26040
>>
>> I hope the backtraces and auto-included info below are enough.
>> Sorry to report and run, but I will have very limited free time
>> for the next two weeks.
>
> The backtraces are from an optimized build, and all the interesting
> values are "optimized out".  Please try reproducing this in an
> unoptimized build, and then submitting a backtrace.

Thanks for looking.
Will do.

> (Also, please note that you opened a second bug with this report.)

Yes, I noticed that and merged them soon after.





  reply	other threads:[~2013-04-26 23:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-25  5:57 bug#14264: 24.3.50; SEGV in char_table_ref's use of SUB_CHAR_TABLE_P Jim Meyering
2013-04-25 16:18 ` Eli Zaretskii
2013-04-26 23:44   ` Jim Meyering [this message]
2013-10-21 23:23   ` Glenn Morris
2013-10-21 23:30     ` Glenn Morris
2013-10-22 16:51     ` Eli Zaretskii
2013-10-22 18:25       ` Glenn Morris
2013-10-22 20:30         ` Eli Zaretskii
2013-10-23  7:53           ` Glenn Morris
2013-10-23 16:40             ` Eli Zaretskii
2014-07-08 17:53               ` Stefan Monnier
2014-07-08 19:33                 ` Eli Zaretskii
2014-07-08 19:42                   ` Jim Meyering
2014-07-08 20:26                     ` Jim Meyering
2014-07-08 20:25                   ` Stefan Monnier

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=87bo90zwkk.fsf@rho.meyering.net \
    --to=jim@meyering.net \
    --cc=14264@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 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).