diff options
| author | Simon Marchi <simon.marchi@ericsson.com> | 2015-06-15 13:34:47 -0400 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@ericsson.com> | 2015-06-15 13:34:47 -0400 |
| commit | cb6f16cf4f7a12f9aadddc0451d47f0511729c8d (patch) | |
| tree | 453ea411f97f59f3f360c6e533c6d4174cee2db5 /gdb/gdbcore.h | |
| parent | 31b7833d205031b52996982f5da025d60c6e052f (diff) | |
Cleanup write_memory doc
This doc about write_memory seems outdated.
gdb/ChangeLog:
* corefile.c (write_memory): Update doc.
* gdbcore.h (write_memory): Same.
Diffstat (limited to 'gdb/gdbcore.h')
| -rw-r--r-- | gdb/gdbcore.h | 6 |
1 files changed, 2 insertions, 4 deletions
diff --git a/gdb/gdbcore.h b/gdb/gdbcore.h index a437c8af7b..0c08b37398 100644 --- a/gdb/gdbcore.h +++ b/gdb/gdbcore.h @@ -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); |