Bugs item #1772468, was opened at 2007-08-12 02:02
Message generated for change (Comment added) made by yooden
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=111005&aid=1772468&group_id=11005
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Program
Group: release
Status: Open
Resolution: Fixed
Priority: 7
Private: No
Submitted By: Bert Wesarg (lebert)
Assigned to: Scott Tringali (tringali)
Summary: core dump when osfInsert in help window
Initial Comment:
NEdit dumps core when the osfInsert key is pressed in a help window. Actually
when the set_overtype_mode() action routine is called from a help window. And
more precisely the setOvertypeModeAP() function. And concrete because there is
no WindowInfo from help windows and therefore window == NULL => SIGSEGV
BTW: I think there may be more such paths over APs from menu.c
NEdit release of Aug 12, 2007
Built on: Linux, 486, GNU C
Built at: Aug 12 2007, 01:50:54
With Motif: 2.2.3 [@(#)Motif Version 2.2.3]
Running Motif: 2.2 [unknown]
Server: The X.Org Foundation 70200000
Visual: 16-bit TrueColor (ID 0x23, Default)
Locale: en_US.UTF-8
----------------------------------------------------------------------
>Comment By: Thorsten Haude (yooden)
Date: 2007-12-27 12:23
Message:
Logged In: YES
user_id=119143
Originator: NO
So can this be closed?
----------------------------------------------------------------------
Comment By: Scott Tringali (tringali)
Date: 2007-08-12 20:14
Message:
Logged In: YES
user_id=11321
Originator: NO
Audited all the translations, this seems to be the only one.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2007-08-12 20:04
Message:
Logged In: NO
This is strange - that should only come from invoking the menu item, and
there's no menu. I went through all the custom keybindings and only
osfInsert caused this.
----------------------------------------------------------------------
Comment By: Nobody/Anonymous (nobody)
Date: 2007-08-12 15:24
Message:
Logged In: NO
Good point - we should probably review the translations and only add the
ones that make sense.
----------------------------------------------------------------------
Comment By: Andrew Hood (ajhood)
Date: 2007-08-12 11:46
Message:
Logged In: YES
user_id=36856
Originator: NO
It would appear that anything that calls WidgetToWindow could wind having
a null pointer returned. That is what is happening here.
Wrapping the code of setOvertypeModeAP in "if (window != NULL) {" etc.
cures this one, but how many other calls to WidgetToWindow need similar
protection?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=111005&aid=1772468&group_id=11005
--
NEdit Develop mailing list - [email protected]
http://www.nedit.org/mailman/listinfo/develop