darkkirb/old-cross-binutils
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Cleanup write_memory doc

Browse source 
This doc about write_memory seems outdated.

gdb/ChangeLog:

	* corefile.c (write_memory): Update doc.
	* gdbcore.h (write_memory): Same.
This commit is contained in:
Simon Marchi 2015-06-15 13:34:47 -04:00
parent 31b7833d20
commit cb6f16cf4f
3 changed files with 9 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
gdb/ChangeLog
View file

@ -1,3 +1,8 @@
2015-06-15 Simon Marchi <simon.marchi@ericsson.com>
* corefile.c (write_memory): Update doc.
* gdbcore.h (write_memory): Same.
2015-06-15 Jan Kratochvil <jan.kratochvil@redhat.com>
* linux-tdep.c (enum filterflags): Make it from anonymous enum.

4
gdb/corefile.c
View file

@ -383,8 +383,8 @@ read_memory_typed_address (CORE_ADDR addr, struct type *type)
return extract_typed_address (buf, type);
}
/* Same as target_write_memory, but report an error if can't
write. */
/* See gdbcore.h. */
void
write_memory (CORE_ADDR memaddr,
const bfd_byte *myaddr, ssize_t len)

6
gdb/gdbcore.h
View file

@ -101,10 +101,8 @@ extern void read_memory_string (CORE_ADDR, char *, int);
CORE_ADDR read_memory_typed_address (CORE_ADDR addr, struct type *type);
/* This takes a char *, not void *. This is probably right, because
passing in an int * or whatever is wrong with respect to
byteswapping, alignment, different sizes for host vs. target types,
etc. */
/* Same as target_write_memory, but report an error if can't
write. */
extern void write_memory (CORE_ADDR memaddr, const gdb_byte *myaddr,
ssize_t len);