From: "Michael Snyder" <msnyder@sonic.net>
To: "Jim Ingham" <jingham@apple.com>
Cc: "Daniel Jacobowitz" <drow@false.org>, <gdb@sourceware.org>
Subject: Re: libSegFault and just in time debugging
Date: Fri, 29 Jun 2007 20:24:00 -0000 [thread overview]
Message-ID: <002001c7ba8b$8f87a340$677ba8c0@sonic.net> (raw)
In-Reply-To: <05236501-9101-47AB-A677-C9D27635BDD4@apple.com>
> Oops, hit send too soon...
>
> Meant to say if you are automatically attaching to everything on the
> system, you have to be careful about auto-launched daemons, because
> they won't die all the way while waiting for the connection to the
> debugger, and that can cause them not to get restarted. Not a problem
> in general with released systems, where hopefully the daemons aren't
> crashing all that often. But with development systems it could cause
> a problem...
Right. But there's considerable flexibility in, eg. at what point in your
boot scripts do you introduce the LD_PRELOAD variable or the
/etc/ld.so.preload file. You could start your system daemons first,
for instance, and then they wouldn't get the preload library. And the
env variable would only apply to children of a specific shell. Could
even be turned on by a user, thus not affecting any root or other-user
processes.
Or, you could introduce the /etc file before boot, and get everything,
thus enabling you to debug crashing system daemons etc.
next prev parent reply other threads:[~2007-06-29 20:24 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 [this message]
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
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='002001c7ba8b$8f87a340$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