[comp.windows.interviews] bug in idraw

sundar@ai.mit.edu (Sundar Narasimhan) (06/20/91)

Hi, If I include the following resource spec in my .Xresources file,
idraw gets a segmentation violation upon startup and dumps core.
Note that the resource spec has nothing to do with idraw. I suspect it 
is caused by some statically allocated array.. Can anyone help me?

Thanks in advance.

xrn*artBindings: \
  ^<Key>v:	artScroll()	\n\
  $<Key>v:	artScrollBack() \n\
  <Key>Delete:	artScrollBack() \n\
  ^<Key>n:	artScrollLine()	\n\
  ^<Key>p:	artScrollBackLine() \n\
  $<Key>0x3E:	artScrollEnd()	\n\
  $<Key>0x3C:	artScrollBeginning()  \n\
  <Key>b:	artScrollBack()		\n\
  <Key>0x20:	doTheRightThing(goto)	\n\
  ^<Key>N:	artSubNext()	\n\
  :<Key>N:	artNext()	\n\
  :<Key>n:	artNextUnread()	\n\
  ^<Key>P:	artSubPrev()	\n\
  <Key>P:	artPrev()	\n\
  :<Key>-:	artLast()	\n\
  :<Key>/:	artSubSearch()	\n\
  <Key>f:	artFollowup()	\n\
  <Key>r:	artReply()	\n\
  <Key>s:	artSave()	\n\
  <Key>w:	artSave()	\n\
  <Key>|:	artSave()	\n\
  <Key>%:	artSave("| uudecode")	\n\
  :<Key>C:	artCancel()	\n\
  :<Key>v:	artHeader()	\n\
  ^<Key>X:	artRot13()	\n\
  :<Key>X:	artRot13()	\n\
  :<Key>c:	artCatchUp()	\n\
  :<Key>j:	artMarkRead()	\n\
  <Key>m:	artMarkUnread()	\n\
  :<Key>k:	artKillSession()	\n\
  :<Key>K:	artKillLocal()	\n\
  :<Key>u:	artUnsub()	\n\
  <Key>.:	artGotoArticle()	\n\
  <Key>q:	artQuit()

linton@marktwain.rad.sgi.com (Mark Linton) (06/21/91)

In article <16568@life.ai.mit.edu>, sundar@ai.mit.edu (Sundar Narasimhan) writes:
|> Hi, If I include the following resource spec in my .Xresources file,
|> idraw gets a segmentation violation upon startup and dumps core.
|> Note that the resource spec has nothing to do with idraw. I suspect it 
|> is caused by some statically allocated array.. Can anyone help me?

This looks like an old propsheet bug.  You should use 3.0-beta, or at least grab
iv/src/lib/InterViews/propsheet.c from it.

When reporting bugs such as this, please be sure to include which version of InterViews
you are using (2.6, 3.0-beta, ...), what platform you are on (Sun, HP700, ...), and what
C++ compiler you are using (cfront 2.0, g++, ...).  Also, we would prefer bug reports be sent
to interviews-bugs@interviews.stanford.edu rather than the entire mailing list.  That way
we can eliminate duplicate postings, post fixes, and keep a log of all the posted bugs.