Re: EMACS_22_BASE: Crash after creating a new frame, gtk_toolbar_set_icon_size?

["Jan D." <jan.h.d@swipnet.se>]

Reiner Steib wrote:
> On Wed, Aug 15 2007, Jan Djärv wrote:
> 
>> Reiner Steib skrev:
> [...]
>>> I got another (probably unrelated) crash when using this patch:
>>> <http://thread.gmane.org/v9ps1pyix4.fsf%40marauder.physik.uni-ulm.de>
>> Please don't link to other places, post the full details here.
> 
> Well, I have posted the full details in the other mail on emacs-devel.
> But as I thought the crashed are not related, I started a new thread.

The backtraces are different.

> 
> ,----[ <news:v9ps1pyix4.fsf@marauder.physik.uni-ulm.de> ]
> | From: Reiner Steib <reinersteib+gmane@imap.cc>
> | Subject: EMACS_22_BASE: Crash during mail composition
> | To: emacs-devel@gnu.org
> | Date: Tue, 14 Aug 2007 22:12:39 +0200
> | Message-ID: <v9ps1pyix4.fsf@marauder.physik.uni-ulm.de>
> `----
> 
>> Can you print font_frame in frame 0?  And if it isn't NULL, *font_frame?
> 
> --8<---------------cut here---------------start------------->8---
> (gdb) frame 0
> #0  0x080ba394 in cmp_font_names (a=0xb21a3c0, b=0xb21a8c0)
>     at [...]/cvs-EMACS_22_BASE/emacs/src/xfaces.c:2715
> 2715              int resy = FRAME_X_DISPLAY_INFO (font_frame)->resy;
> (gdb) print font_frame
> $1 = (struct frame *) 0x0
> (gdb) print *font_frame
> Cannot access memory at address 0x0
> --8<---------------cut here---------------end--------------->8---
> 
> I'm not very familiar with gdb, so please give me the exact gdb
> commands if this was not what you had in mind.
> 

That was it for now, thanks.

	Jan D.