Re: Crashes on w32 and debugging

["Lennart Borgman (gmail)" <lennart.borgman@gmail.com>]

Lennart Borgman (gmail) wrote:
> Jason Rumney wrote:
>>
>>> Program received signal SIGSEGV, Segmentation fault.
>>> 0x0103a4ef in next_element_from_display_vector (it=0x82dbe0) at 
>>> xdisp.c:6063
>>> 6063      if (INTEGERP (*it->dpvec)
>>
>> You might want to do a cvs update before spending too much time 
>> debugging this, as I can't find any such line in the latest version of 
>> xdisp.c. Perhaps the bug has already been fixed.
> 
> I just got a new crash, but unfortunately not running under the 
> debugger. However this crash happened after working mostly in org-mode 
> (I had not started any external programs from Emacs this time).
> 
> I had been using occur quite a lot in the org-mode buffer. I always 
> start it from isearch.
> 
> Remember that the crash when running under the debugger was a SIGSEV in 
> next_element_from_display_vector.
> 
> To avoid confusion I say again that that this is
> 
>  GNU Emacs 23.0.50.1 (i386-mingw-nt5.1.2600) of 2008-01-30 (patched)

Switched to run under gdb and immediately got a new crash. As above 
working in an org-mode buffer. I had just used occur and then I typed 
`C-x 1'. That operation was never made (ie the frame was still divided 
when I switched to the debugger. (Not sure however if the crash actually 
happened before `C-x 1' or after.)

Here are some data as suggested by Jason before:

Program received signal SIGSEGV, Segmentation fault.
0x0103a4ef in next_element_from_display_vector (it=0x82e5d0) at xdisp.c:6063
6063      if (INTEGERP (*it->dpvec)
(gdb) print it
$1 = (struct it *) 0x82e5d0
(gdb) print it->dpvec
$2 = (Lisp_Object *) 0x0
(gdb) print *it->dpvec
Cannot access memory at address 0x0
(gdb)