Bug 60235 - Trivial, correct Xaw program runs wrong with glibc-2.2.90-6
Summary: Trivial, correct Xaw program runs wrong with glibc-2.2.90-6
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: glibc
Version: 1.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-02-22 17:22 UTC by Jonathan Kamens
Modified: 2016-11-24 15:14 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-02-24 23:40:02 UTC
Embargoed:


Attachments (Terms of Use)

Description Jonathan Kamens 2002-02-22 17:22:00 UTC
Save the following as foo.c and compile it with "gcc -g foo.c -L/usr/X11R6/lib
-lXaw -lXt":

-----cut here-----
#include <X11/Intrinsic.h>
#include <X11/Shell.h>
#include <X11/StringDefs.h>
#include <X11/Xaw/AsciiText.h>

XtAppContext context;
Widget top;
Widget text;

main(int argc, char *argv[])
{
  top = XtVaOpenApplication(&context, "Test", NULL, 0, &argc, argv,
			    NULL, sessionShellWidgetClass,
			    XtNgeometry, "=500x500",
			    0);
  text = XtVaCreateManagedWidget("text", asciiTextWidgetClass, top,
				 XtNgeometry, "=500x500",
				 XtNstring, "/etc/termcap",
				 XtNtype, XawAsciiFile,
				 NULL);
  XtRealizeWidget(top);
  XtAppMainLoop(context);
}
-----cut here-----

Now run it with glibc-2.2.90-6.i686.rpm installed.  You will see an empty window
when what you *should* see is a window displaying /etc/termcap.

Now run the same program (you don't even need to recompile it) with
glibc-2.2.4-19.3.i686.rpm installed.  It will run properly, i.e., you'll see
/etc/termcap in the window.

Obviously, this trivial program is not the one I care about :-); it's just a
test case to illustrate a problem I discovered with a much more useful program,
xrn.

In short, glibc-2.2.90-6 is broken.

Comment 1 Jonathan Kamens 2002-02-24 23:39:57 UTC
This problem goes away with the glibc-2.2.90-7 that Jakub asked me to try.



Note You need to log in before you can comment on or make changes to this bug.