help debugging a Emacs crash

help debugging a Emacs crash

[Le Wang]

Hi all,

I'm trying to follow up on a Emacs crash using these repro steps:
https://github.com/victorhge/iedit/pull/31#issuecomment-12451517

I believe Thierry reported the original crash using Linux.  I've
reproed it using Yamamoto's Mac build 24.2.1 and the NS build on the
Git mirror's master branch on OS X 10.8.2.

Here is the backtrace from gdb after the crash:

(gdb) bt
#0  get_pos_property (position=1518142, prop=140734799800208,
object=140734799800208) at editfns.c:402
#1  0x000000010015d489 in get_local_map (position=716,
buffer=0x10500ecda, type=140734799800288) at intervals.c:2234
#2  0x00000001000ad236 in read_key_sequence () at keyboard.c:2799
#3  0x00000001000b05a8 in command_loop_1 () at keyboard.c:1460
#4  0x0000000100115169 in internal_condition_case (bfun=0x1000af1a0
<command_loop_1>, handlers=4320211706, hfun=0x1000b0630 <cmd_error>)
at eval.c:1193
#5  0x00000001000af17e in command_loop_2 (ignore=140734799800840) at
keyboard.c:1175
#6  0x0000000100115265 in internal_catch (tag=140734799800840,
func=0x1000af140 <command_loop_2>, arg=140734799800840) at eval.c:964
#7  0x00000001000b0b90 in command_loop [inlined] () at
/Users/lewang/src/emacs/emacs/src/keyboard.c:1154
#8  0x00000001000b0b90 in recursive_edit_1 () at keyboard.c:787
#9  0x00000001000a17ad in Frecursive_edit () at keyboard.c:851
#10 0x000000010009e668 in main (argc=5312704, argv=0x7fff5fbfefc0) at
emacs.c:1555
(gdb)

I can hold the debugger for a while, but need some advice on what to do next?

-- 
Le

Re: help debugging a Emacs crash

[Eli Zaretskii]

> Date: Sun, 20 Jan 2013 01:30:44 +0800
> From: Le Wang <l26wang@gmail.com>
> 
> I'm trying to follow up on a Emacs crash using these repro steps:
> https://github.com/victorhge/iedit/pull/31#issuecomment-12451517

What is "iedit"?

Re: help debugging a Emacs crash

[Christopher Schmidt]

Eli Zaretskii <eliz@gnu.org> writes:
> What is "iedit"?

https://github.com/eproxus/emacs-iedit/blob/master/iedit.el

        Christopher

Re: help debugging a Emacs crash

[Eli Zaretskii]

> From: Christopher Schmidt <christopher@ch.ristopher.com>
> Date: Sat, 19 Jan 2013 18:04:38 +0000 (GMT)
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> > What is "iedit"?
> 
> https://github.com/eproxus/emacs-iedit/blob/master/iedit.el

Thanks, but could someone please post a reproducible recipe starting
with "emacs -Q"?

Re: help debugging a Emacs crash

[Le Wang]

On Sun, Jan 20, 2013 at 2:40 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> Thanks, but could someone please post a reproducible recipe starting
> with "emacs -Q"?
>

1. clone iedit repo

    git clone -b emacs-crash-repro git@github.com:lewang/iedit.git

2. eval

    (push "." load-path)

3. open up "iedit-rect.el", M-x eval-buffer

4. create temp buffer (C-x b "tempbuf")

5. insert (literally, buffer contents between double-quotes):

"It shouldn't crash no matter what
It shouldn't crash no matter what
It shouldn't crash no matter what
It shouldn't crash no matter what
It shouldn't crash no matter what
"

6. goto point-min

7. C-spc

8. goto point-max

9. C-return

10. this is inf loop.  Wait 5 seconds

11. Press C-g


Crash!!!


-- 
Le

Re: help debugging a Emacs crash

[Eli Zaretskii]

> Date: Sun, 20 Jan 2013 02:59:31 +0800
> From: Le Wang <l26wang@gmail.com>
> Cc: Christopher Schmidt <christopher@ch.ristopher.com>, emacs-devel@gnu.org
> 
> On Sun, Jan 20, 2013 at 2:40 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Thanks, but could someone please post a reproducible recipe starting
> > with "emacs -Q"?
> >
> 
> 1. clone iedit repo
> 
>     git clone -b emacs-crash-repro git@github.com:lewang/iedit.git
> 
> 2. eval
> 
>     (push "." load-path)
> 
> 3. open up "iedit-rect.el", M-x eval-buffer
> 
> 4. create temp buffer (C-x b "tempbuf")
> 
> 5. insert (literally, buffer contents between double-quotes):
> 
> "It shouldn't crash no matter what
> It shouldn't crash no matter what
> It shouldn't crash no matter what
> It shouldn't crash no matter what
> It shouldn't crash no matter what
> "
> 
> 6. goto point-min
> 
> 7. C-spc
> 
> 8. goto point-max
> 
> 9. C-return
> 
> 10. this is inf loop.  Wait 5 seconds
> 
> 11. Press C-g
> 
> 
> Crash!!!

Thanks, this should be fixed now with revision 111560 on the trunk.
(The infloop is still there, but I think that's a bug in iedit, not in
Emacs.)

Re: help debugging a Emacs crash

[Le Wang]

On Sun, Jan 20, 2013 at 1:58 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Sun, 20 Jan 2013 01:30:44 +0800
>> From: Le Wang <l26wang@gmail.com>
>>
>> I'm trying to follow up on a Emacs crash using these repro steps:
>> https://github.com/victorhge/iedit/pull/31#issuecomment-12451517
>
> What is "iedit"?

The code I used to repro the crash is here:
https://github.com/lewang/iedit/tree/emacs-crash-repro

This is the only fork/branch under my control.

-- 
Le

Re: help debugging a Emacs crash

[Le Wang]

On Sun, Jan 20, 2013 at 2:35 AM, Le Wang <l26wang@gmail.com> wrote:
> On Sun, Jan 20, 2013 at 1:58 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>>> Date: Sun, 20 Jan 2013 01:30:44 +0800
>>> From: Le Wang <l26wang@gmail.com>
>>>
>>> I'm trying to follow up on a Emacs crash using these repro steps:
>>> https://github.com/victorhge/iedit/pull/31#issuecomment-12451517
>>
>> What is "iedit"?
>
> The code I used to repro the crash is here:
> https://github.com/lewang/iedit/tree/emacs-crash-repro

Get the source using git:

    git clone -b emacs-crash-repro git@github.com:lewang/iedit.git

> This is the only fork/branch under my control.



-- 
Le

Re: help debugging a Emacs crash

[Eli Zaretskii]

> Date: Sun, 20 Jan 2013 02:43:12 +0800
> From: Le Wang <l26wang@gmail.com>
> Cc: emacs-devel@gnu.org
> 
> Get the source using git:
> 
>     git clone -b emacs-crash-repro git@github.com:lewang/iedit.git

And then do what steps from 'emacs -Q'?