Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Michael Snyder" <msnyder@sonic.net>
To: "Daniel Jacobowitz" <drow@false.org>, "Eli Zaretskii" <eliz@gnu.org>
Cc: <gdb@sourceware.org>
Subject: Re: libSegFault and just in time debugging
Date: Sat, 30 Jun 2007 16:03:00 -0000	[thread overview]
Message-ID: <001301c7bb30$342039e0$677ba8c0@sonic.net> (raw)
In-Reply-To: <20070630154904.GA5952@caradoc.them.org>



> > > 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.

Either way, right now we don't have a JIT debugging technique
for Unix.  The question is, is it worth having one?



  reply	other threads:[~2007-06-30 16:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-29 19:10 Michael Snyder
2007-06-29 19:15 ` Daniel Jacobowitz
2007-06-29 19:52   ` Michael Snyder
2007-06-29 20:00     ` Daniel Jacobowitz
2007-06-29 20:12       ` Jim Ingham
2007-06-29 20:14         ` Jim Ingham
2007-06-29 20:24           ` Michael Snyder
2007-06-29 20:20         ` Michael Snyder
2007-06-30 10:52       ` Eli Zaretskii
2007-06-30 11:49         ` Eli Zaretskii
2007-06-30 15:49         ` Daniel Jacobowitz
2007-06-30 16:03           ` Michael Snyder [this message]
2007-06-30 16:10             ` Mark Kettenis
2007-06-30 18:22             ` Eli Zaretskii
2007-06-30 18:19           ` Eli Zaretskii
2007-06-30 17:28 ` Dave Korn
2007-06-30 21:27   ` Michael Snyder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='001301c7bb30$342039e0$677ba8c0@sonic.net' \
    --to=msnyder@sonic.net \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox