all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Jordi Gutiérrez Hermoso" <jordigh@octave.org>
Cc: 11653@debbugs.gnu.org
Subject: bug#11653: 23.2; Segfault with csv-mode
Date: Wed, 13 Jun 2012 18:45:43 +0300	[thread overview]
Message-ID: <83395zz048.fsf@gnu.org> (raw)
In-Reply-To: <CAPHS2gzh1GmgHBggRC39kyBf--bOAkbNvtRfcFckEs46oL6bXw@mail.gmail.com>

> Date: Wed, 13 Jun 2012 10:32:00 -0400
> From: Jordi Gutiérrez Hermoso <jordigh@octave.org>
> Cc: 11653@debbugs.gnu.org
> 
> >> (gdb) bt
> >> #0  0x0000000000438b03 in handle_face_prop (it=0x7fffffffb0c0) at xdisp.c:3693
> >
> > In frame 0, can you show what does the following GDB command print?
> 
> Sure thing:
> 
>     Program received signal SIGSEGV, Segmentation fault.
>     0x0000000000438649 in handle_face_prop (it=0x7fffffffb180) at xdisp.c:3689
>     3689		= (it->current.overlay_string_index >= 0
>     (gdb) p it->current
>     $1 = {
>       pos = {
>         charpos = 1,
>         bytepos = 1
>       },
>       overlay_string_index = 1935,   <<<<<<<<<<<<<<<<<<<<<<<
>       string_pos = {
>         charpos = 0,
>         bytepos = 0

Are there this many overlay strings in the buffer at character
position 1?  If not, this huge number is probably garbage, and is the
cause for the segfault.

Btw, when I tried your recipe, Emacs asked me about the column to sort
by, which was not in your recipe.  Can you double-check if your recipe
is 100% correct and does not omit any important details?






  reply	other threads:[~2012-06-13 15:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08 16:29 bug#11653: 23.2; Segfault with csv-mode Jordi Gutiérrez Hermoso
2012-06-08 17:49 ` Eli Zaretskii
2012-06-13 14:32   ` Jordi Gutiérrez Hermoso
2012-06-13 15:45     ` Eli Zaretskii [this message]
2012-06-13 16:12       ` Jordi Gutiérrez Hermoso
2012-06-13 16:28         ` Eli Zaretskii
2012-06-15 18:13         ` Eli Zaretskii
2012-06-15 18:30           ` Eli Zaretskii
2012-06-16 10:28             ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83395zz048.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=11653@debbugs.gnu.org \
    --cc=jordigh@octave.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.