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 Date: Wed, 9 Jun 2004 15:32:28 -0600 From: paul cannon To: cygwin AT cygwin DOT com Subject: Re: Weird problem with gdb 2003-09-20-cvs (cygwin-special) Message-ID: <20040609213228.GA1526@nafpik.com> Reply-To: paul DOT cannon AT sdl DOT usu DOT edu, paul AT nafpik DOT com, cygwin AT cygwin DOT com References: <0706F4CDC397BF4483877BFDA8DBD3A54622A5 AT kjsdemucshrexc1 DOT eu DOT pm DOT com> <20040602150415 DOT GD5787 AT coe DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040602150415.GD5787@coe.casa.cgf.cx> User-Agent: Mutt/1.5.6+20040523i On Wed, Jun 02, 2004 at 11:04:15AM -0400, Christopher Faylor wrote: > On Wed, Jun 02, 2004 at 10:06:06AM +0200, Demmer, Thomas wrote: > >(gdb) run > >Starting program: /m/c/insi.exe > > > >Program received signal SIGSEGV, Segmentation fault. > >0x77e75a3f in KERNEL32!IsBadWritePtr () from > >/c/WINDOWS/system32/kernel32.dll > > Just continue through this error. IsBadWritePtr throws a SEGV > exception. This is normal. The problem, at least for me, is that with the new Cygwin 1.5.10, these are getting generated very frequently in some code. We have a large Motif (well, LessTif) app at work which runs on Cygwin, and with the new DLL, we get dozens of these segfaults under gdb before we can get to the point we're trying to debug. It makes using gdb almost prohibitively difficult. Is there some way to tell gdb *once* to ignore all of these? If not, is there anything else that can be done to make debugging simple again? -- paul -- 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/