From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 9760@debbugs.gnu.org
Subject: bug#9760: 24.0.50; crash
Date: Sat, 15 Oct 2011 15:44:15 -0400 [thread overview]
Message-ID: <E1RFA9X-0005gZ-C1@fencepost.gnu.org> (raw)
In-Reply-To: <83lisnjk5b.fsf@gnu.org> (message from Eli Zaretskii on Sat, 15 Oct 2011 00:14:24 +0200)
Can you tell what does "bzr revno" show in your bzr branch from which
you built this binary?
106087.
I'm confused by the fact that you say you
fetched the sources today, but emacs-version still shows 24.0.50, when
it should have been 24.0.90.
That may be because I did not do a bootstrap recently. It takes a long time.
I just compiled the C and Lisp files.
If this is crucial, I will do a bootstrap tonight to check.
But I think that the fact that I'm running on a Longxin (MIPS-like)
rather than an x86 is more likely to make the difference.
Here is the backtrace.
#0 0x0043ff40 in set_cursor_from_row (w=0x8ee928, row=0xc558cc,
matrix=0x8eef58, delta=0, delta_bytes=0, dy=0, dvpos=0) at xdisp.c:13693
#1 0x00477390 in redisplay_window (window=9365805, just_this_one_p=1)
at xdisp.c:14856
#2 0x0047ae50 in redisplay_window_1 (window=12933324) at xdisp.c:13571
#3 0x006180f0 in internal_condition_case_1 (
bfun=0x47ae0c <redisplay_window_1>, arg=9365805, handlers=9297766,
hfun=0x439964 <redisplay_window_error>) at eval.c:1537
#4 0x00463940 in redisplay_internal () at xdisp.c:13196
#5 0x00464014 in redisplay () at xdisp.c:12343
#6 0x0057adec in read_char (commandflag=1, nmaps=2, maps=0x7fa404e0,
prev_event=9315578, used_mouse_menu=0x7fa40528, end_time=0x0)
at keyboard.c:2443
#7 0x0057eb94 in read_key_sequence (keybuf=0x7fa40608, bufsize=30,
prompt=9315578, dont_downcase_last=0, can_return_switch_frame=1,
fix_current_buffer=1) at keyboard.c:9282
#8 0x00581938 in command_loop_1 () at keyboard.c:1447
#9 0x0061853c in internal_condition_case (bfun=0x581398 <command_loop_1>,
handlers=9346626, hfun=0x58333c <cmd_error>) at eval.c:1499
#10 0x005810ac in command_loop_2 (ignore=<value optimized out>)
at keyboard.c:1158
#11 0x00618698 in internal_catch (tag=<value optimized out>,
func=0x581050 <command_loop_2>, arg=9315578) at eval.c:1256
#12 0x005836e4 in recursive_edit_1 () at keyboard.c:1137
#13 0x00583944 in Frecursive_edit () at keyboard.c:821
#14 0x00568a10 in main (argc=1, argv=0x7fa40de4) at emacs.c:1706
--
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
Use free telephony http://directory.fsf.org/category/tel/
next prev parent reply other threads:[~2011-10-15 19:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 21:41 bug#9760: 24.0.50; crash Richard Stallman
2011-10-14 22:14 ` Eli Zaretskii
2011-10-15 19:44 ` Richard Stallman [this message]
2011-10-15 20:56 ` Eli Zaretskii
2011-10-16 11:19 ` Richard Stallman
2011-10-16 12:40 ` Eli Zaretskii
2011-10-16 21:40 ` Richard Stallman
2011-10-17 3:55 ` 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=E1RFA9X-0005gZ-C1@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=9760@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).