public inbox for insight-prs@sourceware.org help / color / mirror / Atom feed
From: lyons.chang@gmail.com To: insight-gnats@sources.redhat.com Cc: lchang@juniper.net Subject: insight/291: Multiple users impact each other when debugging with insight in the same Linux. Date: Mon, 27 Mar 2006 09:03:00 -0000 [thread overview] Message-ID: <20060327085840.27989.qmail@sourceware.org> (raw) >Number: 291 >Category: insight >Synopsis: Multiple users impact each other when debugging with insight in the same Linux. >Confidential: no >Severity: critical >Priority: high >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Mar 27 09:03:01 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Lyons Chang >Release: insight-6.4 insigh-CVS-6.4.5 >Organization: >Environment: GNU/Linux on x86. I have tested this issue under Debian31/Ubuntu5.04/CentOS4.1/CentOS4.2. This should be a common issue. >Description: If 2 persons login to one Linux host and both debug with a insight, they will impact each other. For instance, one person close his insight, other insight instances are closed, too. One person issue "step over", others also step over. very stange. 2 insight instance in 2 vnc sessions in the same machine will also have this behaviour. More stange is that 2 insight spawned by same person always work fine. I have tested with gdb6.4, it works well. "step over" does not impact each other. Insight 6.1 does not have this issue. and I have not found insight 6.2 & 6.3 to test. >How-To-Repeat: 2 persons login to one Linux host and both start debugging with insight. Please contact me if you can not reproduce it. This is really a critical issue. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2006-03-27 9:03 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-03-27 9:03 lyons.chang [this message] 2006-11-30 23:19 kseitz
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=20060327085840.27989.qmail@sourceware.org \ --to=lyons.chang@gmail.com \ --cc=insight-gnats@sources.redhat.com \ --cc=lchang@juniper.net \ /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: linkBe 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).