From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 15036@debbugs.gnu.org
Subject: bug#15036: 24.3.50; emacs_backtrace.txt
Date: Wed, 07 Aug 2013 07:08:21 +0300 [thread overview]
Message-ID: <83li4euoqy.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SQpATYK7-wqd6MEOzapAY1AZp1nPb1VA32Oy3dJiLDV=g@mail.gmail.com>
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Tue, 6 Aug 2013 22:15:19 +0200
> Cc: 15036@debbugs.gnu.org
>
> > Backtrace:
>
> w32_backtrace at w32fns.c:7990
> emacs_abort at w32fns.c:8022
> terminate_due_to_signal at emacs.c:369
> die at alloc.c:6558
> unwind_create_frame at w32fns.c:4252
> do_unwind_create_frame at w32fns.c:4263
> unbind_to at eval.c:3300
> unwind_to_catch at eval.c:1118
> Fthrow at eval.c:1145
> Ftop_level at keyboard.c:1200
> Ffuncall at eval.c:2813
> exec_byte_code at bytecode.c:905
> funcall_lambda at eval.c:3050
> Ffuncall at eval.c:2865
> apply1 at eval.c:2582
> Fcall_interactively at callint.c:381
> Ffuncall at eval.c:2823
> exec_byte_code at bytecode.c:905
> funcall_lambda at eval.c:2984
> Ffuncall at eval.c:2865
> call1 at eval.c:2615
> command_loop_1 at keyboard.c:1560
> internal_condition_case at eval.c:1302
> command_loop_2 at keyboard.c:1161
> internal_catch at eval.c:1076
> command_loop at keyboard.c:1132
> recursive_edit_1 at keyboard.c:779
> Frecursive_edit at keyboard.c:843
> Ffuncall at eval.c:2813
> exec_byte_code at bytecode.c:905
> funcall_lambda at eval.c:2984
> Ffuncall at eval.c:2865
> Fapply at eval.c:2355
> apply1 at eval.c:2589
> call_debugger at eval.c:324
> maybe_call_debugger at eval.c:1716
> Fsignal at eval.c:1536
> xsignal at eval.c:1571
> xsignal2 at eval.c:1592
> wrong_type_argument at data.c:188
> CHECK_STRING at lisp.h:2382
> string_match_1 at search.c:381
> Fstring_match at search.c:452
> Ffuncall at eval.c:2823
> exec_byte_code at bytecode.c:905
> funcall_lambda at eval.c:2984
> apply_lambda at eval.c:2925
> eval_sub at eval.c:2231
> Feval at eval.c:2005
> eval_dyn at keyboard.c:7563
> internal_condition_case_1 at eval.c:1339
> menu_item_eval_property at keyboard.c:7574
> parse_menu_item at keyboard.c:7750
> single_menu_item at menu.c:329
> map_keymap_item at keymap.c:566
> map_keymap_internal at keymap.c:605
> map_keymap_canonical at keymap.c:670
> single_keymap_panes at menu.c:295
> parse_single_submenu at menu.c:551
> set_frame_menubar at w32menu.c:454
> initialize_frame_menubar at w32menu.c:621
> w32_window at w32fns.c:4155
This is a duplicate of 14861.
prev parent reply other threads:[~2013-08-07 4:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 18:15 bug#15036: 24.3.50; emacs_backtrace.txt Drew Adams
2013-08-06 20:15 ` Juanma Barranquero
2013-08-07 4:08 ` Eli Zaretskii [this message]
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=83li4euoqy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15036@debbugs.gnu.org \
--cc=lekktu@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).