This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: 1.5.6-pre: Occasional bad memory accesses within cygwin1.dll


On Wed, Dec 31, 2003 at 11:38:08AM -0500, Christopher Faylor wrote:
> On Wed, Dec 31, 2003 at 10:02:44AM -0500, Pierre A. Humblet wrote:
> >Christopher Faylor wrote:
> >>>Oh.  This is probably with current CVS, which is broken.  Known problem.
> >>>It's why I haven't generated a snapshot yet.
> >
> >>This should be fixed now.  I'm uploading a snapshot.
> >
> >CYGWIN_ME-4.90 hpn5170x 1.5.6s(0.108/3/2) 20031231 01:31:40 i686 unknown
> >unknown Cygwin
> >
> >Now virtually every cygwin program (/bin/true, ls, uname,...) almost
> >always ends with the popup about causing an error in Cygwin1.dll. 
> 
> Did you look at the changes I made?  It's difficult to believe that minor
> changes to cygwin.din would cause a popup on every access, although I can
> believe that the stuff in CVS previously would work that way.  If anything,
> I'd expect that there would be no change rather than actual worsening.
> 
> Are you sure you're up to date?

It's straight from the snapshot, no cvs involved.

Pierre



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]