[Top][All Lists]

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

Re: Building Emacs-cvs on Cygwin

From: Kim F. Storm
Subject: Re: Building Emacs-cvs on Cygwin
Date: Sun, 01 Oct 2006 01:34:37 +0200
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux)

Eli Zaretskii <address@hidden> writes:

>> Date: Thu, 28 Sep 2006 12:18:00 +0200 (MET DST)
>> From: Angelo Graziosi <address@hidden>
>> cc: address@hidden, address@hidden
>> The problem is localized between lines 
>>    1072      # People get bothered when...
>>    .....     .....
>>    1110      end
> This is somewhat tangential to the real problem at hand, but as long
> as we are talking about this: what happens if you remove all that
> block from .gdbinit, type "gdb ./emacs.exe" in the src directory, and
> then manually type the commands in the offending block, one after the
> other?  I'm particularly interested to know whether you see any error
> messages from GDB, and if so, which line causes these messages.
>> (gdb) xpr
>> Lisp_Symbol
>> $2 = (struct Lisp_Symbol *) 0x7d8bf888
>> Cannot access memory at address 0x7d8bf88c
>> (gdb) 
> Kim, any clever ideas, before we ask Angelo to look in last_marked[]
> array etc.?

Turning off the toolbar makes the crash go away, so I suspect a GC
problem with building the tool-bar string.

It could be a specific tool-bar binding in one of the keymaps that
triggers the bug.

Could we try to dump global-map, and all active local maps and look
for tool-bar items (using eval) in them ?

Does Cygwin use GCPROs or stack marking?

>> I want to flag that on Cygwin mailing list there are peoples that have
>> similar problems with GDB
>> (http://cygwin.com/ml/cygwin/2006-09/msg00534.html).
> Yes, I've seen that thread, but I don't see any useful (i.e., that
> explain what's going on and why) responses to the problem it reported.

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

reply via email to

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