Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Dave Korn" To: Subject: RE: MapViewOfFileEx errors with cygwin1-20040716 snapshot Date: Thu, 22 Jul 2004 18:41:16 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-reply-to: Message-ID: X-OriginalArrivalTime: 22 Jul 2004 17:41:16.0312 (UTC) FILETIME=[16D76180:01C47013] > -----Original Message----- > From: cygwin-owner On Behalf Of Igor Pechtchanski > Sent: 22 July 2004 18:13 > > Never mind. I spoke too soon, and my "current CVS" turned out to be not > all that current. The message above comes from pinfo.cc, line 197. Oops. Teach me to deal with mail in the order it arrives! > > Would it work if I built my own DLL, with debugging, and inserted a > "try_to_debug()" call before the api_fatal()? Frankly, > I've never had > much luck getting gdb to start from the "error_start" setting in > $CYGWIN, but I'll see if I can get this to work unless the > above info > helps someone track this down sooner. > Dunno exactly. However, my suggestion is that the most useful diagnostic at that point would be a print out of the address parameter passed to the MVOFx function and the name of the .dll that is occupying that area, or perhaps just an entire module list. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/