On Fri, Oct 29, 2004 at 01:28:58PM +0100, Dave Korn wrote: >> -----Original Message----- >> From: cygwin-owner On Behalf Of Igor Pechtchanski >> Sent: 28 October 2004 17:24 > >> On Thu, 28 Oct 2004, jdeifik wrote: >> >> > > On Wed, 27 Oct 2004, jdeifik wrote: >> > > >> > > > When I run the program with gdb, I get really weird segmentation >> > > > faults, for example: >> > > >> > > http://www.cygwin.com/ml/cygwin/2004-10/msg01033.html >> >> Does anyone know gdb macros well enough to say off-hand whether it's >> possible to write a function to ignore those particular SEGVs? > > I dunno the language syntax, but I can see the design: set a breakpoint on >IsBadWritePtr, and have a macro routine that is called by that breakpoint, >that 1) issues the 'handle' instruction 2) issues a 'finish' to step until >out of IsBadWritePtr 3) cancels the 'handle' instruction 4) issues a 'cont' >to let the app continue running.
You're both thinking outside of the box here. Please stop that. The correct way to look at this is "Why doesn't someone FIX gdb????" Please get with the program and close the box cover. You're just frightening people by peering outside of that "they should fix it for me" box. 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/
