darlinghq/darling-gdb
1
0
Fork 0
mirror of https://github.com/darlinghq/darling-gdb.git synced 2024-11-29 15:00:34 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

* valprint.c (val_print_string): If errcode is set, always print

Browse Source 
an error, regardless of force_ellipsis.  In the non-EIO case,
	just print the error message rather than calling error().  Don't
	access *(bufptr-1) if bufptr points to the start of the buffer.
	When looking for '\0', don't increment bufptr and addr if bufptr
	started out already at limit.  If an error happens on fetching the
	first character, don't print the string.
This commit is contained in:
Jim Kingdon 1994-03-01 18:56:33 +00:00
parent e3d6ec4a0d
commit c84539ee9c
1 changed files with 0 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/valprint.c
View File

@ -728,10 +728,6 @@ val_print_string (addr, len, stream)
struct cleanup *old_chain = NULL; /* Top of the old cleanup chain. */
char peekchar; /* Place into which we can read one char. */
/* If errcode is non-zero, this is the address which failed to read
successfully. */
CORE_ADDR err_addr;
/* First we need to figure out the limit on the number of characters we are
going to attempt to fetch and print. This is actually pretty simple. If
LEN is nonzero, then the limit is the minimum of LEN and print_max. If
@ -777,7 +773,6 @@ val_print_string (addr, len, stream)
/* Read as much as we can. */
nfetch = target_read_memory_partial (addr, bufptr, nfetch, &errcode);
err_addr = addr + nfetch;
if (len != 0)
{
addr += nfetch;