This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Problem with unsigned char * data
- From: Emilio Ugo GIUFFRIDA <emilio dot giuffrida at st dot com>
- To: <gdb at sources dot redhat dot com>
- Cc: <emilio dot giuffrida at st dot com>
- Date: Thu, 20 May 2004 20:08:24 +0200
- Subject: Problem with unsigned char * data
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:
(gdb) print pt1
$6 =
Error: Error in st200emu : Cannot read buffer at memory adress 0xffffffff
Adaptor error on: read memory access at address (Exception 5 while executing ROM command)
It seems that gdb tries to read at 0xffffffff and, for pointers to unsigned char, displays by default the string pointed.
Do you know if there is a gdb option disabling this behaviour?
Best regards,
Emilio
--------------------------------------------------------------------------
Emilio Ugo Giuffrida
ST200 Tools Team Phone : +39 0957404514
CMG/MCDT Software Design Center Fax : +39 0957404013
ST Microelectronics TINA : 052 4514
Stradale Primosole, 50 e-mail : emilio.giuffrida@st.com
95121 Catania ITALY
--------------------------------------------------------------------------