From: Nix <nix@esperi.org.uk>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 10617@debbugs.gnu.org
Subject: bug#10617: 24.0.92; Bidi crash reading a message from emacs-devel
Date: Tue, 31 Jan 2012 18:06:38 +0000 [thread overview]
Message-ID: <8739av691t.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <83aa53rg6k.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 31 Jan 2012 18:26:59 +0200")
On 31 Jan 2012, Eli Zaretskii verbalised:
>> From: Nix <nix@esperi.org.uk>
>> Cc: 10617@debbugs.gnu.org
>> Date: Tue, 31 Jan 2012 14:21:22 +0000
>>
>> (gdb) xsymbol
>> $2 = (struct Lisp_Symbol *) 0xb81a20
>> There is no member named data.
>
> You are using a bad .gdbinit file, or somehow botched the definition
> of xsymbol or one of the commands it invokes. How about doing a
> "source .gdbinit" after you verify that .gdbinit comes from the same
> tree from which you produced the Emacs binary?
Well, I'm in the build tree's src subdirectory and xsymbol is defined,
so I'm not sure where else it could be coming from! It's not like I have
multiple .gdbinits lying around that define xsymbol :) I tried sourcing
./.gdbinit explicitly: it changes nothing.
But unfortunately my attempt to reproduce this bug with the same message
have failed so far (it must be dependent on something else in Emacs
state, probably something transient), and the coredump is naturally not
compatible with an Emacs built without optimization. So this probably
needs to be closed as unreproducible :(
--
NULL && (void)
prev parent reply other threads:[~2012-01-31 18:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 22:40 bug#10617: 24.0.92; Bidi crash reading a message from emacs-devel Nix
2012-01-27 9:03 ` Eli Zaretskii
2012-01-30 18:14 ` Nix
2012-01-30 19:03 ` Eli Zaretskii
2012-01-30 19:11 ` Nix
2012-01-30 19:26 ` Andreas Schwab
2012-01-30 21:09 ` Eli Zaretskii
2012-01-30 21:39 ` Nix
2012-01-31 3:46 ` Eli Zaretskii
2012-01-31 14:21 ` Nix
2012-01-31 16:26 ` Eli Zaretskii
2012-01-31 18:06 ` Nix [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8739av691t.fsf@spindle.srvr.nix \
--to=nix@esperi.org.uk \
--cc=10617@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.