From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 15962@debbugs.gnu.org
Subject: bug#15962: 24.3.50; emacs_backtrace.txt
Date: Mon, 25 Nov 2013 07:53:43 -0800 (PST) [thread overview]
Message-ID: <5a4902b7-cb15-4088-9307-dcf1fb3008b7@default> (raw)
In-Reply-To: <<83ppppb18u.fsf@gnu.org>>
> > > The backtrace looks bogus, btw:
> > Not sure what you mean by that.
>
> Line 161 in w32menu.c is this:
> { <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>
> Line 451 in emacs.c is this:
> name = Fexpand_file_name (Vinvocation_name, dir); <<<<<<<<<<<
>
> and it does not call anything in w32menu.c. Etc. and etc.: this
> simply cannot be a valid sequence of call-stack frames.
I see. The code that generates such a "bogus" backtrace would seem
to be somewhat mistaken or incorrect, in that case.
But the backtrace, however inaccurate, is genuine - not at all bogus;
I can assure you of that.
next parent reply other threads:[~2013-11-25 15:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<6e5659a6-23f6-435a-847d-fbd4c611fcba@default>
[not found] ` <<83ppppb18u.fsf@gnu.org>
2013-11-25 15:53 ` Drew Adams [this message]
2013-11-25 17:27 ` bug#15962: 24.3.50; emacs_backtrace.txt Eli Zaretskii
[not found] ` <<3c580e82-9684-4f9b-b63f-bc9750a9e326@default>
[not found] ` <<bd117a36-e822-4883-a117-e56d8640e8f8@default>
[not found] ` <<83mwktb11f.fsf@gnu.org>
2013-11-25 22:21 ` Drew Adams
2013-11-25 22:23 ` Drew Adams
2013-11-26 3:46 ` Eli Zaretskii
[not found] <<386b5655-1318-4a87-b474-0501cd200411@default>
[not found] ` <<83y54989ld.fsf@gnu.org>
2013-11-28 5:41 ` Drew Adams
[not found] <<0691bec9-b582-4681-8245-ee3d05225485@default>
[not found] ` <<83d2llakw6.fsf@gnu.org>
2013-11-27 16:18 ` Drew Adams
2013-11-27 16:43 ` Eli Zaretskii
[not found] ` <<0abd6b16-9da4-46db-bc2d-e35ec6808ed8@default>
[not found] ` <<8361rdaiyc.fsf@gnu.org>
2013-11-28 2:24 ` Drew Adams
2013-11-28 3:54 ` Eli Zaretskii
[not found] <<2797d3c5-cea9-4015-8cd6-f72da142a1d7@default>
[not found] ` <<83eh62a4er.fsf@gnu.org>
2013-11-27 5:59 ` Drew Adams
2013-11-27 15:59 ` Drew Adams
2013-11-27 16:49 ` Eli Zaretskii
2013-11-27 16:07 ` Eli Zaretskii
[not found] <<4ff8d3cf-d427-47ee-9efb-cef8041879a7@default>
[not found] ` <<83txez9kj9.fsf@gnu.org>
2013-11-27 3:29 ` Drew Adams
2013-11-27 3:51 ` Eli Zaretskii
[not found] <<80b4c0b0-836e-475d-9bdc-d4abca9d03f7@default>
[not found] ` <<2daccc5f-1289-412b-abf3-44c2fc8aec52@default>
[not found] ` <<831u23bz9t.fsf@gnu.org>
2013-11-26 14:15 ` Drew Adams
2013-11-26 16:48 ` Eli Zaretskii
[not found] <<5a4902b7-cb15-4088-9307-dcf1fb3008b7@default>
[not found] ` <<838uwcbddg.fsf@gnu.org>
2013-11-25 17:39 ` Drew Adams
[not found] <<aa6e506b-d912-4d16-835f-33d2cd7d24c1@default>
[not found] ` <<83siulbkvd.fsf@gnu.org>
2013-11-24 22:27 ` Drew Adams
2013-11-24 23:33 ` Drew Adams
2013-11-25 1:05 ` Drew Adams
2013-11-25 3:41 ` Eli Zaretskii
2013-11-25 3:37 ` Eli Zaretskii
2013-11-24 0:32 Drew Adams
2013-11-24 20:33 ` 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=5a4902b7-cb15-4088-9307-dcf1fb3008b7@default \
--to=drew.adams@oracle.com \
--cc=15962@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).