From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 13743@debbugs.gnu.org
Subject: bug#13743: 24.2.93; Segmentation fault when trying to [s]teal a file opened elsewhere
Date: Wed, 20 Feb 2013 21:31:37 +0200 [thread overview]
Message-ID: <83ehgaok86.fsf@gnu.org> (raw)
In-Reply-To: <5122CCEB.8000206@yandex.ru>
> Date: Tue, 19 Feb 2013 04:52:59 +0400
> From: Dmitry Gutov <dgutov@yandex.ru>
> CC: 13743@debbugs.gnu.org
>
> On 18.02.2013 20:11, Eli Zaretskii wrote:
> > Can you recompile without optimizations, and show the backtrace from
> > that build? Thanks.
>
> Here you go:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x0000000000653481 in add_properties (plist=32025878, i=0x0,
> object=31976325)
> at textprop.c:378
> 378 for (tail2 = i->plist; CONSP (tail2); tail2 = Fcdr (XCDR (tail2)))
> (gdb) bt full
> #0 0x0000000000653481 in add_properties (plist=32025878, i=0x0,
> object=31976325) at textprop.c:378
> tail1 = 32025878
> tail2 = 31873526
> sym1 = 13125730
> val1 = 12886562
> changed = 0
> found = 0
> gcpro1 = {
> next = 0x7fffffff6180,
> var = 0x57dc19 <modify_region+481>,
> nvars = 4295010134
> }
> gcpro2 = {
> next = 0x7fffffff6180,
> var = 0x57dc19 <modify_region+481>,
> nvars = 4295010134
> }
> gcpro3 = {
> next = 0x7fffffff6180,
> var = 0x57dc19 <modify_region+481>,
> nvars = 4295010134
> }
> ---Type <return> to continue, or q <return> to quit---
> #1 0x0000000000655963 in Fadd_text_properties (start=4, end=3068,
> properties=32025878, object=31976325) at textprop.c:1212
> i = 0x0
> unchanged = 0x7fffffffa568
> s = 1
> len = 558
> modified = 19
> gcpro1 = {
> next = 0xa31e4d <pure+1297709>,
> var = 0xa31e29 <pure+1297673>,
> nvars = 579820584989
> }
> #2 0x00000000006559e0 in Fput_text_property (start=4, end=3068,
> property=13125730, value=12886562, object=12886562) at textprop.c:1229
> No locals.
Thanks. This shows quite a different story. But the backtrace alone
is not enough to figure out what goes wrong in this scenario and why,
at least not for me (and I don't see anyone else jumping in to dig
into this problem). And since reproducing this involves tricky
non-default setup and an external package, I wonder if you could
provide a recipe starting with "emacs -Q" or with a minimal .emacs
init file, and show every command you type to reproduce the crash?
> By the way, is there an easier way to compile without optimizations than
> assigning CFLAGS before running configure?
That's the canonical way, AFAIK.
next prev parent reply other threads:[~2013-02-20 19:31 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 6:41 bug#13743: 24.2.93; Segmentation fault when trying to [s]teal a file opened elsewhere Dmitry Gutov
2013-02-18 16:11 ` Eli Zaretskii
2013-02-19 0:52 ` Dmitry Gutov
2013-02-20 19:31 ` Eli Zaretskii [this message]
2013-02-21 8:30 ` Dmitry Gutov
2013-02-18 19:35 ` Glenn Morris
2013-02-19 0:55 ` Dmitry Gutov
2013-02-21 5:16 ` Paul Eggert
2013-02-21 7:03 ` Dmitry Gutov
2013-02-23 3:37 ` Dmitry Gutov
2013-02-23 15:10 ` Eli Zaretskii
2013-02-23 16:59 ` Stefan Monnier
2013-02-23 18:44 ` Eli Zaretskii
2013-02-24 15:28 ` Dmitry Gutov
2013-02-24 15:50 ` Eli Zaretskii
2013-02-25 5:52 ` Dmitry Gutov
2013-02-25 15:25 ` Stefan Monnier
2013-02-25 16:37 ` Eli Zaretskii
2013-02-25 18:29 ` Stefan Monnier
2013-02-25 18:56 ` Eli Zaretskii
2013-02-25 20:28 ` Stefan Monnier
2013-02-26 3:39 ` Eli Zaretskii
2013-02-26 4:35 ` Stefan Monnier
2013-03-02 9:30 ` Eli Zaretskii
2013-02-25 16:25 ` Eli Zaretskii
2013-02-25 18:27 ` Dmitry Gutov
2013-02-25 16:27 ` Eli Zaretskii
2013-02-25 19:08 ` Dmitry Gutov
2013-02-25 19:31 ` Eli Zaretskii
2013-02-25 23:23 ` Dmitry Gutov
2013-02-26 3:51 ` Eli Zaretskii
2013-02-26 3:59 ` Dmitry Gutov
2013-02-26 18:42 ` Eli Zaretskii
2013-02-27 17:46 ` Dmitry Gutov
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=83ehgaok86.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13743@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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).