hugues henocq wrote: > I wanted to upgrade my cygwin version from 1.3.17 to 1.5.17 and, then, > I tried > to compil and link my software using X/lesstif GUI. The link works but I > get some new messages like this: > ... > Then, when I run the software, it fails down with a segmentation fault. > The problem happens in an Xm.... > function and I think that aoto-mport doesn't run correctly ? > > Linked under the previous version (1.3.17) or under linux, my software > works very well. > So, I think that there is a regression between these 2 versions.
Between 1.3.17 and 1.5.17 there have been something like 22 intermediate releases and 30 months of time, so I don't think it's very fair to expect that not much has changed. :-) That said, the entire Cygwin/X suite works fine so if there was a problem linking to lesstif I think it would have affected other packages too. If you were using a Cygwin that old chances are the gcc and binutils used were also ancient as well, and things do change there too. For example, starting in 3.3.3-3 gcc places const structures in .rdata, and this will cause a fault if the structure contains a pointer to an object imported from another DLL since that requires a relocation fixup. I don't mean to imply that's the problem you're facing (esp since that results in a windows error and not a segfault), but your report doesn't really give enough information to know what's going on. All we really have is that it used to work, and now it segfaults. We don't know what the code is trying to do, or how it was compiled or linked, etc. I think that you'll have to either provide a testcase that reproduces the fault, or try to narrow down the problem some more. Brian