X-Spam-Check-By: sourceware.org From: "Dave Korn" To: Subject: RE: seg fault in cygwin1.dll during gdb session Date: Mon, 6 Mar 2006 17:39:51 -0000 Message-ID: <058601c64144$f8b54a50$a501a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <371110DD79C65F4D8AD5C5DF65CF25E60CB2C7@mainserver.Wivision-Tech.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk 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 06 March 2006 17:25, Shmuel Vagner wrote: > HI, > I am using a SlickEdit IDE to compile and debug my projects. > When debugging a new operator gdb reports a segmentation fault. > I found this problem in the archives and the proposed solution is to > ignore the fault and continue debugging. > Unfortunately this is possible with gdb or ddd but not with slic (No CLI > there). > My question: Is there a patch for this By "this", do you mean "the sheer utter mind-boggling insanity of the design of slic"? Or something else? > and how can I install it (does it > involves building Cygwin from source or is there another simpler way)? There's nothing wrong with Cygwin. The problem is that slic was designed by an insane gibbering maniac and coded by a team of hairy handed programmers just when it happened to be a full moon. The solution would be to shoot it with a silver bullet or drive a stake through its heart. Seriously, though, I find it beyond the bounds of credibility to believe that someone has actually built an IDE that has a built in debugger that doesn't give you any means to continue the program after it hits a breakpoint. Perhaps you have misunderstood how to operate slic? 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/