X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 28 May 2008 16:33:21 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: MS or cygwin dll debug tools/ was "sys/sockio.h" etc. Message-ID: <20080528203321.GA12799@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20080523000735 DOT GA23793 AT ednor DOT casa DOT cgf DOT cx> <483BBE3D DOT EDF663D3 AT dessent DOT net> <483D7849 DOT 5010505 AT sbcglobal DOT net> <483D7C01 DOT EAE5ADA1 AT dessent DOT net> <483DB6E0 DOT 53C6EED0 AT dessent DOT net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <483DB6E0.53C6EED0@dessent.net> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Wed, May 28, 2008 at 12:47:44PM -0700, Brian Dessent wrote: >Mike Marchywka wrote: > >> (gdb) b *0x0401000 >> Breakpoint 1 at 0x401000 >> (gdb) run >> Starting program: /cygdrive/e/new/temp/nmap/src3/nmap-4.62/a.exe >> >> Program received signal SIGSEGV, Segmentation fault. >> >> Program received signal SIGSEGV, Segmentation fault. >> >> Program received signal SIGSEGV, Segmentation fault. >> >> Program exited with code 0200. >> You can't do that without a process to debug. >> (gdb) > >The fact that it never actually begins execution therefore implies that >it encounters a fault by the OS loader during process initialization, >such as the "const data in .rdata needing relocation due to >auto-imports" situation. I bet that if you invoke it via strace or >from a native command prompt (not bash) you will see a dialog box >explaining the fault since the "SetErrorMode (SEM_FAILCRITICALERRORS)" >stuff won't be active. Aren't we still talking about using msvcrt and cygwin1 in the same application where something like a SIGSEGV prior to initialization would be the expected consequences of mixing the two dlls? I'd think it likely that either msvcrt or cygwin1.dll to become confused during dll initialization if one or the other was present. cgf -- 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/