From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1021 invoked by alias); 14 Feb 2008 17:09:16 -0000 Received: (qmail 1012 invoked by uid 22791); 14 Feb 2008 17:09:16 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 14 Feb 2008 17:08:54 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id CAF3498140; Thu, 14 Feb 2008 17:08:52 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id B45B39811F; Thu, 14 Feb 2008 17:08:52 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1JPhZs-00010G-2U; Thu, 14 Feb 2008 12:08:52 -0500 Date: Thu, 14 Feb 2008 17:09:00 -0000 From: Daniel Jacobowitz To: Gordon Prieur Cc: gdb@sourceware.org Subject: Re: stop-on-solib-events and Cygwin (or MinGW) Message-ID: <20080214170852.GA3552@caradoc.them.org> Mail-Followup-To: Gordon Prieur , gdb@sourceware.org References: <47B473F8.5050401@sun.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47B473F8.5050401@sun.com> User-Agent: Mutt/1.5.17 (2007-12-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-02/txt/msg00099.txt.bz2 On Thu, Feb 14, 2008 at 09:01:44AM -0800, Gordon Prieur wrote: > Hi, > > I've just added support to the NetBeans gdb module for breakpoints > set in shared libraries explicity dlopened (as apposed to shared libraries > linked at link time). I'm using stop-on-solib-events to do this, and it > works > fine on both Solaris and Linux. Why do you need to do this? i.e. what are you doing with breakpoints that current versions of GDB don't handle for you? (There may be a good reason, I'm just curious what it is.) > However, if I set this property on Windows I don't get stopped after > my dlopen/dlclose calls. Is there any way (on Windows) to make this > feature work? The alternative is to provide a complete 2nd implementation > for Windows (based on stopping in dlopen, calling "finish", and comparing > info share from before and after). Since stack information isn't always > reliable on Windows, I'm concerned this method won't be very reliable. > > Are there technical reasons why stop-on-solib-events doesn't work on > Windows? Or is it just unimplemented on that platform? Would I see the > same behavior on Vista? It's just unimplemented. However, you might want to try a current CVS snapshot. I think it should work now that Pedro switched win32 over to XML-based libraries. -- Daniel Jacobowitz CodeSourcery