[Top][All Lists]

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

Re: Crashes on w32 and debugging

From: Jason Rumney
Subject: Re: Crashes on w32 and debugging
Date: Fri, 29 Feb 2008 23:16:08 +0000
User-agent: Thunderbird (Windows/20080213)

Lennart Borgman (gmail) wrote:
Now I got a crash. Could you please tell me what to examine and how to do it?

Program received signal SIGSEGV, Segmentation fault.
0x0103a4ef in next_element_from_display_vector (it=0x82dbe0) at xdisp.c:6063
6063      if (INTEGERP (*it->dpvec)

Start by examining the C variables around the point where it crashes, looking for any obvious problems like null pointers. The "print" command will print values, as I wrote in my previous mail. A good start would be:

print it
print it->dpvec
print *it->dpvec

reply via email to

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