emacs-pretest-bug
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: segfault in read_process_output() during vc-diff


From: Kim F. Storm
Subject: Re: segfault in read_process_output() during vc-diff
Date: Tue, 07 Nov 2006 15:23:50 +0100
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.90 (gnu/linux)

Tim Van Holder <address@hidden> writes:

> I was committing a set of changes using vc-directory, and v-= caused
> the emacs window to disappear.  Re-ran from the commandline, crash was
> reproducible as a segfault.  Re-ran under debugger; emacs opens the diff
> window just fine, then a SIGSEGV gets flagged in bcopy(), called at line
> 5144 of process.c. I have been unable to reproduce the crash on anything
> other than this single file - all other files can be compared using
> vc-diff just fine.
>
> xbacktrace produces no output
>
> bt full output:
>
> #0  0x40895af0 in bcopy () from /lib/libc.so.6
> No symbol table info available.
> #1  0x081864d4 in read_process_output (proc=143372852, channel=<value 
> optimized out>) at /home/tim/gnu/src/emacs/src/process.c:5144
>         odeactivate = 137457249
>         text = 142872947
>         outer_running_asynch_code = 0
>         waiting = -1
>         nbytes = <value optimized out>
>         outstream = 137502441
>         old = (struct buffer *) 0x88fb2b8
>         p = (struct Lisp_Process *) 0x88bb230
>         opoint = <value optimized out>
>         coding = (struct coding_system *) 0x88fb4c0
>         carryover = -1316

This looks very suspicious.

Can you print the "coding" variable and the "p" variable:

up 1
p *coding
p *p


-- 
Kim F. Storm <address@hidden> http://www.cua.dk





reply via email to

[Prev in Thread] Current Thread [Next in Thread]