Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!snorkelwacker.mit.edu!bloom-beacon!eru!kth.se!cyklop.nada.kth.se!news
From: d88-hba@nada.kth.se (Harald Barth)
Newsgroups: comp.windows.open-look
Subject: Bug in olgx (was: Re: devGUIDE Core Dumping! HELP!)
Keywords: xview
Message-ID: <1991Jun12.095822.29016@nada.kth.se>
Date: 12 Jun 91 09:58:22 GMT
Sender: news@nada.kth.se (Mr News)
Reply-To: d88-hba@nada.kth.se (Harald Barth)
Organization: Royal Institute of Technology, Stockholm, Sweden
Lines: 44


Brent Browning:
	 In Mike's case the problem is a bug in olgx, the OPEN LOOK
	graphics library.  It only happens in monochrome and it only happens
	when you have a glyph of some sort.  His interface had a glyph in a 
	button and he has a monocrome monitor.  If your stack trace ends
	up in olgx_draw_text, you're being bit.

Exactly, me too.

Brent Browning:
 	  I know that the bug is fixed in OpenWindows V3.  There is rumored
	to be a patch, I'm looking around for it.

Good, I need that bug fixed. Maybe I could get some help from the rumoring 
people. Big SMILE.


More detailed bug description:

I built my application built with devguide.
It consists of 3 controls and 1 canvas.
In the controls I got 1 button with attached menu and in another a button with
a glyph. 
I generate C++ code witg gxv++ or c code with gxv (doesn`t matter).
I use the generated Makefile.
The application dumps (SEGFAULT) when I press the menubutton. This happens only
when the *other* button has a glyph (instead  of text label)


I had the following experience with debuggers on this problem:

-xdbx exits when reading the symbolic info
-dbxtool dies quietly
-gdb deadlocks everything
-dbx prints a stack trace ending up in olgx_draw_text() (as above). dbx does not run.

The whole scenario was the same with olwm(Sun 4) or twm(Sun3, Sun4).
----------------------

Thanks, Harald.
(d88-hba@nada.kth.se)

---------------------