From: "Michael Snyder" <msnyder@sonic.net>
To: "Jim Ingham" <jingham@apple.com>, "Daniel Jacobowitz" <drow@false.org>
Cc: <gdb@sourceware.org>
Subject: Re: libSegFault and just in time debugging
Date: Fri, 29 Jun 2007 20:20:00 -0000 [thread overview]
Message-ID: <001a01c7ba8a$f5e49540$677ba8c0@sonic.net> (raw)
In-Reply-To: <D5C4B767-2A6C-4CDD-901C-A67B112F6E6A@apple.com>
[Daniel Jacobowitz]
> FYI, cygwin already does this, too; it can invoke dumper (to
> generate core dumps) or GDB.
That's right -- I'd forgotten about that.
[Jim Ingham:]
> We did this with Mac OS X for a while (the way Mach Exceptions work
> it's a little easier to implement, you don't need a special library or
> anything like that). It's pretty neat. We were doing it
> automatically with all processes on the system, which is even handier,
> but you do have to be careful - if you are attaching with gdb rather
> than dumping core.
Of course the old Mac model ("macsbug"?) is the classic instance
of just in time debugging. And then (surprise), Windows had it too!
I'm just wondering if linux/unix users might not like to have the same
thing.
Michael
next prev parent reply other threads:[~2007-06-29 20:20 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 [this message]
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
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='001a01c7ba8a$f5e49540$677ba8c0@sonic.net' \
--to=msnyder@sonic.net \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=jingham@apple.com \
/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