Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Emilio Ugo GIUFFRIDA <emilio.giuffrida@st.com>
Cc: gdb@sources.redhat.com
Subject: Re: Problem with unsigned char * data
Date: Thu, 20 May 2004 21:14:00 -0000	[thread overview]
Message-ID: <20040520211418.GA13414@nevyn.them.org> (raw)
In-Reply-To: <000001c43e95$75dd67b0$9a8182a4@CTN000514>

On Thu, May 20, 2004 at 08:08:24PM +0200, Emilio Ugo GIUFFRIDA wrote:
> Gentlemen,
> 
> I have a problem with gdb/Insight :-(
> 
> On a board, when a "unsigned char *" pointer is badly initialized to 
> 0xffffffff( that for us is outside the memory ), trying to print the pointer's value in the local variable window or in the watchpoint window makes the GUI crash.
> 
> Using the gdb console, the answer is quite verbose, but correct:

You probably want to send this to the Insight list then.

> Do you know if there is a gdb option disabling this behaviour?

I don't think so.

-- 
Daniel Jacobowitz


  reply	other threads:[~2004-05-20 21:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-20 18:09 Emilio Ugo GIUFFRIDA
2004-05-20 21:14 ` Daniel Jacobowitz [this message]
2004-05-21 15:25 ` Andrew Cagney

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=20040520211418.GA13414@nevyn.them.org \
    --to=drow@false.org \
    --cc=emilio.giuffrida@st.com \
    --cc=gdb@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