Re: problems killing a gnuclient frame

Tuesday, 20 March 2001

Richard Zatorski <razl(a)dazl.eng.sun.com&gt; writes:

...
 This is the same problem I've had before with the gnu server. 
When I
 fire it up, i run gnuclient to create a new frame.  When I exit
 that frame, the whole server dumps core with a sigbus. 
Just a sanity check: Are you using display-time? (Your crash seems
different though).

...
 #12 0xfef855f4 in CallGetValuesHook () from
/usr/openwin/lib/libXt.so.4
 #13 0xfef8526c in XtGetValues () from /usr/openwin/lib/libXt.so.4
 #14 0x1ab768 in x_set_frame_text_value ()
 #15 0x1ae060 in x_set_title_from_bufbyte ()
 #16 0x114468 in update_frame_title ()
 #17 0x1686bc in redisplay_frame ()
 #18 0x1688a8 in redisplay_device ()
 #19 0x168cac in redisplay_without_hooks ()
 #20 0x16e828 in redisplay () 
Any chanche you could inspect the local variables and see which frame
it trying to update the frame title for? one suspects the old one...

jan

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998