Re: Pre 1.5.3-1 static libs (was cygwin 1.5.3-1 and xfree devel)
On Fri, Sep 12, 2003 Christopher Faylor wrote: > On Fri, Sep 12, 2003 Brian Ford wrote: > >>If confirmed, a short note to cygwin-apps may be in order, adding packages >>containing static libraries that make system calls whose arguments have >>changed size to the list of ASAP rebuilds. >> >You mean another note to go with the 27 other times this was mentioned? > Ok, I thought I had been keeping up with the requirements fairly closely. I guess I was a bit slow to put 2 and 2 together with respect to static libs. I thought other package maintainers might have been also. Sorry. >>(Wish I would have helped make this a compile time, rather than link time >>feature. Lazy me.) > >One of us is really confused as to why making this compile time versus >link time would be a wonderful thing. I guess you could do something >like "#define stat stat64" in a header file but that comes with its own >set of problems. > Maybe. It is just the same set of problems that most UNIX vendors I work with chose. Thus, it's more familiar to me, and I would guess others too. >Suffice it to say that we chose to go with a link time solution since, >IMO, it is the best solution. The problem with libraries was a known >one prior to releasing 1.5.x and we are all competent enough programmers >to understand that we could mess around with headers and play with >ifdefs and defines. We chose not to. > Ok. I give. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: Pre 1.5.3-1 static libs (was cygwin 1.5.3-1 and xfree devel)
On Fri, Sep 12, 2003 at 02:06:52PM -0500, Brian Ford wrote: >If confirmed, a short note to cygwin-apps may be in order, adding packages >containing static libraries that make system calls whose arguments have >changed size to the list of ASAP rebuilds. You mean another note to go with the 27 other times this was mentioned? >(Wish I would have helped make this a compile time, rather than link time >feature. Lazy me.) One of us is really confused as to why making this compile time versus link time would be a wonderful thing. I guess you could do something like "#define stat stat64" in a header file but that comes with its own set of problems. Suffice it to say that we chose to go with a link time solution since, IMO, it is the best solution. The problem with libraries was a known one prior to releasing 1.5.x and we are all competent enough programmers to understand that we could mess around with headers and play with ifdefs and defines. We chose not to. cgf
Pre 1.5.3-1 static libs (was cygwin 1.5.3-1 and xfree devel)
After building my own cygwin1.dll with debugging info, I think I figured out my problem with xfree devel and Cygwin 1.5.3-1 here: http://www.cygwin.com/ml/cygwin-xfree/2003-09/msg00204.html The Xt library is a pre 1.5.3-1 static one. It calls stat. At link time, my test app links with Xt and its stat call is redirected to stat64 incorrectly, thus corrupting the stack. This appears true indeed via gdb and my debugable cygwin1.dll. Even so, could one of the more knowledgeable developers confirm my suspicion. If confirmed, a short note to cygwin-apps may be in order, adding packages containing static libraries that make system calls whose arguments have changed size to the list of ASAP rebuilds. Thanks for listening. (Wish I would have helped make this a compile time, rather than link time feature. Lazy me.) -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
Re: cygwin 1.5.3-1 and xfree devel
Ok, I finally tracked this down.
Breakpoint 27, 0x005e6340 in stat ()
(gdb) bt
#0 0x005e6340 in stat ()
#1 0x005a865f in TestFile ()
#2 0x005a89c1 in XtFindFile ()
#3 0x005a8e6e in XtResolvePathname ()
#4 0x005c4af8 in CombineAppUserDefaults ()
#5 0x005c5310 in XtScreenDatabase ()
#6 0x005c5eb4 in _XtDisplayInitialize ()
#7 0x005c30d8 in XtOpenDisplay ()
#8 0x005c32f8 in _XtAppInit ()
#9 0x005a9d88 in _XtVaOpenApplication ()
#10 0x005a9ffb in XtVaAppInitialize ()
#11 0x004a5e7e in XvssAppInitialize (argc=0x22fdb8, argv=0x10032788)
at ../../../visual/util/libXutil/Xsupp.c:46
#12 0x00483518 in main (argc=1, argv=0x10032788)
at ../../../visual/util/host/HE_MW.c:1496
#13 0x61005018 in _libkernel32_a_iname ()
#14 0x610052ed in _libkernel32_a_iname ()
#15 0x005e5f82 in cygwin_crt0 ()
#16 0x0040103c in mainCRTStartup ()
#17 0x77e814c7 in _libkernel32_a_iname ()
(gdb) c
Continuing.
Breakpoint 28, 0x005a865f in TestFile ()
(gdb) bt
#0 0x005a865f in TestFile ()
(gdb)
so, the call to stat from TestFile is corrupting the stack, but why? To
my knowledge, libXt is a 1.3.22 compiled library and so should be using
the compatability interface for stat, no?
Any of the developers from the main list care to comment? Thanks.
On Mon, 8 Sep 2003, Brian Ford wrote:
> Just to humor me, can someone else running Cygwin 1.5.3-1 confirm that a
> simple X11 based "hello world program" is broken. If confirmed, I will
> start digging to locate the offending functions, but I'd rather just wait
> for Harold to release a 1.5.3-1 compiled Xfree86 set of packages. Thanks.
>
> On Fri, 5 Sep 2003, Brian Ford wrote:
>
> > When compiled under cygwin 1.5.3-1, the following hello world Motif
> > program gets a SEGV in XtAppInitialize. Harold, what's your time
> > table for a 1.5.3 built Xfree so I can test and update lesstif? Thanks.
> >
> > #include
> > #include
> >
> > XtAppContext context;
> > XmStringCharSet char_set=XmSTRING_DEFAULT_CHARSET;
> >
> > main(argc, argv)
> > int argc;
> > char *argv[];
> > {
> > Widget toplevel, label;
> > XmString S;
> >
> > /* Create an application shell. */
> > toplevel = XtAppInitialize(&context,"",NULL,0,&argc,argv,NULL,
> > NULL,0);
> >
> > /* Create the Label widget. */
> > label = XmCreateLabel(toplevel,"label",NULL,0);
> > S = XmStringCreateLtoR("Hello World!", char_set);
> > XtVaSetValues(label,
> > XmNlabelString, S,
> > NULL);
> >
> > XtRealizeWidget(toplevel);
> > XtAppMainLoop(context);
> > }
> >
> > (gdb) r
> > Starting program: /home/ford/xtest.exe
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x in ?? () from
> > (gdb) bt
> > #0 0x in ?? () from
> >
> >
>
>
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax: 314-551-8444
RE: cygwin 1.5.3-1 and xfree devel
FWIW, It fails the same for me.
Latest 1.5.3-1 (as of this morning.)
Latest XFree86 (as of this morning.)
-David.
-
David Dawson
[EMAIL PROTECTED]
703-367-3885
-Original Message-
From: Brian Ford [mailto:[EMAIL PROTECTED]
Sent: Monday, September 08, 2003 12:16 PM
To: [EMAIL PROTECTED]
Subject: Re: cygwin 1.5.3-1 and xfree devel
Just to humor me, can someone else running Cygwin 1.5.3-1 confirm that a
simple X11 based "hello world program" is broken. If confirmed, I will
start digging to locate the offending functions, but I'd rather just
wait
for Harold to release a 1.5.3-1 compiled Xfree86 set of packages.
Thanks.
On Fri, 5 Sep 2003, Brian Ford wrote:
> When compiled under cygwin 1.5.3-1, the following hello world Motif
> program gets a SEGV in XtAppInitialize. Harold, what's your time
> table for a 1.5.3 built Xfree so I can test and update lesstif?
Thanks.
>
> #include
> #include
>
> XtAppContext context;
> XmStringCharSet char_set=XmSTRING_DEFAULT_CHARSET;
>
> main(argc, argv)
> int argc;
> char *argv[];
> {
> Widget toplevel, label;
> XmString S;
>
> /* Create an application shell. */
> toplevel = XtAppInitialize(&context,"",NULL,0,&argc,argv,NULL,
> NULL,0);
>
> /* Create the Label widget. */
> label = XmCreateLabel(toplevel,"label",NULL,0);
> S = XmStringCreateLtoR("Hello World!", char_set);
> XtVaSetValues(label,
> XmNlabelString, S,
> NULL);
>
> XtRealizeWidget(toplevel);
> XtAppMainLoop(context);
> }
>
> (gdb) r
> Starting program: /home/ford/xtest.exe
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x in ?? () from
> (gdb) bt
> #0 0x in ?? () from
>
>
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax: 314-551-8444
Re: cygwin 1.5.3-1 and xfree devel
Just to humor me, can someone else running Cygwin 1.5.3-1 confirm that a
simple X11 based "hello world program" is broken. If confirmed, I will
start digging to locate the offending functions, but I'd rather just wait
for Harold to release a 1.5.3-1 compiled Xfree86 set of packages. Thanks.
On Fri, 5 Sep 2003, Brian Ford wrote:
> When compiled under cygwin 1.5.3-1, the following hello world Motif
> program gets a SEGV in XtAppInitialize. Harold, what's your time
> table for a 1.5.3 built Xfree so I can test and update lesstif? Thanks.
>
> #include
> #include
>
> XtAppContext context;
> XmStringCharSet char_set=XmSTRING_DEFAULT_CHARSET;
>
> main(argc, argv)
> int argc;
> char *argv[];
> {
> Widget toplevel, label;
> XmString S;
>
> /* Create an application shell. */
> toplevel = XtAppInitialize(&context,"",NULL,0,&argc,argv,NULL,
> NULL,0);
>
> /* Create the Label widget. */
> label = XmCreateLabel(toplevel,"label",NULL,0);
> S = XmStringCreateLtoR("Hello World!", char_set);
> XtVaSetValues(label,
> XmNlabelString, S,
> NULL);
>
> XtRealizeWidget(toplevel);
> XtAppMainLoop(context);
> }
>
> (gdb) r
> Starting program: /home/ford/xtest.exe
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x in ?? () from
> (gdb) bt
> #0 0x in ?? () from
>
>
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax: 314-551-8444
cygwin 1.5.3-1 and xfree devel
When compiled under cygwin 1.5.3-1, the following hello world Motif
program gets a SEGV in XtVaAppInitialize. Harold, what's your time
table for a 1.5.3 built Xfree so I can test and update lesstif? Thanks.
#include
#include
XtAppContext context;
XmStringCharSet char_set=XmSTRING_DEFAULT_CHARSET;
main(argc, argv)
int argc;
char *argv[];
{
Widget toplevel, label;
XmString S;
/* Create an application shell. */
toplevel = XtAppInitialize(&context,"",NULL,0,&argc,argv,NULL,
NULL,0);
/* Create the Label widget. */
label = XmCreateLabel(toplevel,"label",NULL,0);
S = XmStringCreateLtoR("Hello World!", char_set);
XtVaSetValues(label,
XmNlabelString, S,
NULL);
XtRealizeWidget(toplevel);
XtAppMainLoop(context);
}
(gdb) r
Starting program: /home/ford/xtest.exe
Program received signal SIGSEGV, Segmentation fault.
0x in ?? () from
(gdb) bt
#0 0x in ?? () from
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax: 314-551-8444
