From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 345 invoked by alias); 22 Jul 2004 17:42:46 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 331 invoked from network); 22 Jul 2004 17:42:46 -0000 Received: from unknown (HELO NUTMEG.CAM.ARTIMI.COM) (217.40.111.177) by sourceware.org with SMTP; 22 Jul 2004 17:42:46 -0000 Received: from mace ([192.168.1.25]) by NUTMEG.CAM.ARTIMI.COM with Microsoft SMTPSVC(6.0.3790.0); Thu, 22 Jul 2004 18:41:16 +0100 From: "Dave Korn" To: Subject: RE: MapViewOfFileEx errors with cygwin1-20040716 snapshot Date: Thu, 22 Jul 2004 17:53:00 -0000 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] X-SW-Source: 2004-07/txt/msg00892.txt.bz2 > -----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/