public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: kseitz@sources.redhat.com
To: insight-prs@sources.redhat.com, kseitz@sources.redhat.com,
	lchang@juniper.net, lyons.chang@gmail.com,
	nobody@sources.redhat.com
Subject: Re: insight/291: Multiple users impact each other when debugging with insight in the same Linux.
Date: Thu, 30 Nov 2006 23:19:00 -0000	[thread overview]
Message-ID: <20061130231901.24039.qmail@sourceware.org> (raw)

Synopsis: Multiple users impact each other when debugging with insight in the same Linux.

Responsible-Changed-From-To: unassigned->kseitz
Responsible-Changed-By: kseitz
Responsible-Changed-When: Thu Nov 30 23:19:01 2006
Responsible-Changed-Why:
    mine
State-Changed-From-To: open->closed
State-Changed-By: kseitz
State-Changed-When: Thu Nov 30 23:19:01 2006
State-Changed-Why:
    I thought I responded to this, but maybe that was on the mailing list. Anyway, the trick is to disable Insight's IPC option. It is really quite unnerving to me that this was implemented that way, but it was. I don't consider it very useful, anyway, so I never even noticed the problem. Change Preferences->Advanced...->IPC Support and disable it. Alternative to change it for everyone (by default -- users with a preference file will still need to disable it manually), edit $INSTALLDIR/share/insight1.0/prefs.tcl and change the setting on the line that starts "pref define gdb/ipc/enabled" to "0".

http://sourceware.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=insight&pr=291


             reply	other threads:[~2006-11-30 23:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-30 23:19 kseitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-27  9:03 lyons.chang

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=20061130231901.24039.qmail@sourceware.org \
    --to=kseitz@sources.redhat.com \
    --cc=insight-gnats@sources.redhat.com \
    --cc=insight-prs@sources.redhat.com \
    --cc=lchang@juniper.net \
    --cc=lyons.chang@gmail.com \
    --cc=nobody@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).