public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: "Andrew Raybould" <ajr@thales.com>
To: kseitz@sources.redhat.com
Cc: insight-prs@sources.redhat.com,
Subject: Re: insight/303: insight always quit itself when I debug
Date: Mon, 14 May 2007 16:53:00 -0000	[thread overview]
Message-ID: <20070514165301.19283.qmail@sourceware.org> (raw)

The following reply was made to PR insight/303; it has been noted by GNATS.

From: "Andrew Raybould" <ajr@thales.com>
To: <insight-gnats@sources.redhat.com>
Cc:  
Subject: Re: insight/303: insight always quit itself when I debug
Date: Mon, 14 May 2007 12:47:35 -0400

 I get this with Insight 6.6, but have no corresponding problem when I
 use gdb, even the one that has been built in the insight bin directory.
 
 Here's a test program (compiled with the command line g++ -g itest.C -o
 itest):
 
 int main () {
   char *p =3D (char*)0;
   return 0;
 }
 
 To trigger the problem, break on the return statement, and then either:
    a. Select the expression '*p' in the second line.
    b. Float the pointer over the highlighted expression. So long as it
 is over the '*', it shows 'p=3D(char*)0', but as soon as it touches the
 'p', the assertion fires.
 
    Or try to set *p as a watch expression.
 
 In gdb, the equivalent actions, 'p *p' and 'watch *p', simply elicit
 'Cannot access memory at address 0x0'.
 
 The system:
 
 uname -a
 Linux XXX 2.6.9-42.ELsmp #1 SMP Wed Jul 12 23:32:02 EDT 2006 x86_64
 x86_64 x86_64 GNU/Linux
 
 
 
 
 
 CONFIDENTIALITY AND SECURITY NOTICE
 
 This e-mail contains information that may be confidential and =
 proprietary. It is to be read and used solely by the intended =
 recipient(s). Thales, Temujin and their affiliates retain all =
 proprietary rights they may have in the information. If you are not an =
 intended recipient, please notify us immediately either by reply e-mail =
 or by telephone at 212-509-3111 and delete this e-mail (including any =
 attachments hereto) immediately without reading, disseminating, =
 distributing or copying. We cannot give any assurances that this e-mail =
 and any attachments are free of viruses and other harmful code. Thales =
 and Temujin reserve the right to monitor, intercept and block all =
 communications involving its computer systems.
 
 


             reply	other threads:[~2007-05-14 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-14 16:53 Andrew Raybould [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-30 22:53 kseitz
2006-10-26  7:33 gliferhan

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=20070514165301.19283.qmail@sourceware.org \
    --to=ajr@thales.com \
    --cc=insight-prs@sources.redhat.com \
    --cc=kseitz@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).