Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com content-class: urn:content-classes:message Subject: RE: Setup.exe release-candidate MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Date: Sun, 17 Mar 2002 16:42:49 +1100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Setup.exe release-candidate Thread-Index: AcHM7FpiBY+ukrKQRmuqpXVbSOEcrwAiOsFQ From: "Robert Collins" To: "Jan Nieuwenhuizen" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g2H6G3a10308 > -----Original Message----- > From: Jan Nieuwenhuizen [mailto:janneke@gnu.org] > Sent: Sunday, March 17, 2002 12:13 AM > To: Robert Collins > Cc: cygwin@cygwin.com > Subject: Re: Setup.exe release-candidate > > > "Robert Collins" writes: > > Hi Robert, > > I think I've reported this too, about a month ago. I've got an old > (P133) windows98 box here, that still exhibits this problem. Cool. > > This REQUIRES volunteer assistance from the set of cygwin setup.exe > > users that have windows 98SE available to them. > > > I will guide, tutor,provide builds and source and debug > commentary - > > in realtime if needed - to get this solved, but I am > physically unable > > do this myself. > > Ok, that sounds like fun, I'll have a go. Though I'm no fan > of Windows programming, nor GUIs, and had hoped someone with > better iron would step forward to debug this. > > Any hints up front on how to use gud, ie, what to put in > .emacs to make ntemacs happy with Cygwin? I've no idea, being a vimmer myself. However, here's the first steps to troubleshoot this (and we'd probably better take this off-line too). build setup in your local sandbox. Then to invoke setup under the debugger run $ gdb -nw ./setup.exe to invoke a windowless gdb. I find this much better for debugging GUI apps than the GUI debugger, but that's just me :}. I strongly suspect that the fault is being caused by my saving and restoring the GDI clip region. so.. msdn is your entry point to the calls I'm used - You might try inserting a breakpoint at PickPackageLine::paint which is where the main clipping manipulation goes on and then skipping the SelectClipRgn calls. (Or just #ifdef that out). Have a fiddle, and get back to me. On second thoughts, MSDN just glared at me, I need a little bit of OS-specific code that may (or may not) solve the problem. I'll try a new snapshot with the appropriate code in 'sight-unseen' and if that helps.... Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/