lesstif

[Harold L Hunt II]

Hold up... am I not reading something correctly?  Was the binutils 
change that caused the problem ever reverted?  If not, the problem will 
still exist.  I never heard that the change was reverted, so I'm 
wondering why binutils being up to date matters at all.  IIRC, with the 
binutils change in place, the only way to address the issue would be to 
change nedit to no longer do a relocs in now-non-writable data, which 
would probably take a week.

I seem to recall that I did everything you asked and it had some new 
problem (which I think was a crash on opening a file, or some such) so I 
decided to set it aside for a few days and promptly forgot about it.

Look, the history doesn't matter.  The point here is that I won't let 
someone release a version of lesstif that breaks nedit... now, if you're 
sure that nedit works just fine with your new lesstif build, then that's 
the end of the story, and we can stop trying to resurrect a conversation 
history.  But, I mentioned that I would *like* you to do one more thing, 
which is to install nedit and lesstif on a machine that has no other 
modifications from you and just make sure that nedit still works and 
that you can actually open files; this might take 15 minutes, which is 
less time then we've spent talking about it.  If it works, fine, 
proceed... if it doesn't work, fine, but proceed with caution and don't 
post a new 'curr' release of lesstif until you've fixed the problem with 
nedit.

Deal?

Harold

Brian Ford wrote:
> On Fri, 16 Sep 2005, Dave Korn wrote:
> 
> 
>>----Original Message----
>>
>>>From: Brian Ford
>>>Sent: 15 September 2005 23:20
>>
>>>I am confused, though.  The crash you presented to me was one of not being
>>>able to start nedit at all:
>>>
>>>Date: Fri, 01 Jul 2005 17:09:32 -0700
>>>From: Harold L Hunt
>>>To: Brian.Ford
>>>Subject: Re: lesstif update request
>>>
>>>Nope, 0.94.4 doesn't work with nedit:
>>>
>>>---------------------------
>>>nedit.exe - Application Error
>>>---------------------------
>>>The application failed to initialize properly (0xc0000005). Click on OK
>>>to terminate the application.
>>
>>  That was the binutils relocs-in-non-writable-.rodata sections problem,
>>wasn't it?
> 
> 
> Exactly, and I explained that to Harold in this not-yet-quoted private
> message from the thread in July (heavily snipped to be concise):
> 
> Date: Tue, 05 Jul 2005 13:11:30 -0700
> From: Harold L Hunt
> To: Brian Ford
> Subject: Re: lesstif update request
> 
> 
>>On Fri, 1 Jul 2005, Harold L Hunt wrote:
>>
>>
>>>The application failed to initialize properly (0xc0000005). Click on OK
>>>to terminate the application.
>>
>>Looks like this could be caused by gcc >= 3.3.3 putting const variables
>>containing addresses of imported DLL symbols into .rdata (which then can't
>>be magically relocated at run time since they end up in a read only
>>section) as discussed here:
>>
>>http://sources.redhat.com/ml/cygwin/2004-09/msg01101.html
>>
>>That was a libtool specific example, but I believe the problem is a
>>general one.
> 
> 
> Yup, that sounds like it describes the problem... and I remember reading
> that thread a while back, but I guess I didn't catch the connection.
> 
> [end quoted message]
> 
> This is exactly why I suspected it was a problem with his binutils or gcc
> packages being out-of-date.  It is also why I am so confused about him
> saying I need to play around with nedit to make it crash?
>