From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31247 invoked by alias); 30 Jun 2007 16:10:47 -0000 Received: (qmail 31238 invoked by uid 22791); 30 Jun 2007 16:10:47 -0000 X-Spam-Check-By: sourceware.org Received: from sibelius.xs4all.nl (HELO brahms.sibelius.xs4all.nl) (82.92.89.47) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 30 Jun 2007 16:10:44 +0000 Received: from brahms.sibelius.xs4all.nl (kettenis@localhost.sibelius.xs4all.nl [127.0.0.1]) by brahms.sibelius.xs4all.nl (8.14.0/8.14.0) with ESMTP id l5UGAP1t021882; Sat, 30 Jun 2007 18:10:25 +0200 (CEST) Received: (from kettenis@localhost) by brahms.sibelius.xs4all.nl (8.14.0/8.14.0/Submit) id l5UGAP2a015281; Sat, 30 Jun 2007 18:10:25 +0200 (CEST) Date: Sat, 30 Jun 2007 16:10:00 -0000 Message-Id: <200706301610.l5UGAP2a015281@brahms.sibelius.xs4all.nl> From: Mark Kettenis To: msnyder@sonic.net CC: drow@false.org, eliz@gnu.org, gdb@sourceware.org In-reply-to: <001301c7bb30$342039e0$677ba8c0@sonic.net> (msnyder@sonic.net) Subject: Re: libSegFault and just in time debugging References: <003c01c7ba81$2abc9ce0$677ba8c0@sonic.net> <20070629191522.GA2715@caradoc.them.org> <000501c7ba87$0e543760$677ba8c0@sonic.net> <20070629200000.GA6453@caradoc.them.org> <20070630154904.GA5952@caradoc.them.org> <001301c7bb30$342039e0$677ba8c0@sonic.net> 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: 2007-06/txt/msg00359.txt.bz2 > From: "Michael Snyder" > Cc: > > > > > FYI, cygwin already does this, too; it can invoke dumper (to generate > core > > > > dumps) or GDB. > > > > > > By Cygwin does this using a Windows-specific technique, doesn't it? > > > > Sure. But LD_PRELOAD is a Unix-specific technique. I don't think > > there's any way around it - when you want to deal with program crashes > > and exceptions, you do something at least a bit platform specific. LD_PRELOAD is actually ELF-specific. > Either way, right now we don't have a JIT debugging technique > for Unix. The question is, is it worth having one? Given that the question pops up every now and then on the mailing list, I'd say it is (even if I've never felt the desire for it myself). Mark