diff options
| author | Ilya Leoshkevich <iii@linux.ibm.com> | 2023-07-19 13:27:45 +0200 |
|---|---|---|
| committer | Ilya Leoshkevich <iii@linux.ibm.com> | 2023-11-24 12:26:16 +0100 |
| commit | fa1c74b22aa8c465974ddf792395d8e313199a52 (patch) | |
| tree | 00ab09e997c05ddf6b69add1ada77f10c095ec56 /gdb/compile/compile-object-run.h | |
| parent | 2ec31e54dff83130fbde8d2f674469078ee203d5 (diff) | |
| download | gdb-fa1c74b22aa8c465974ddf792395d8e313199a52.zip gdb-fa1c74b22aa8c465974ddf792395d8e313199a52.tar.gz gdb-fa1c74b22aa8c465974ddf792395d8e313199a52.tar.bz2 | |
gdb: Fix "target file /proc/.../cmdline contained unexpected null characters"
When using the gcore command, GDB prints the following warning:
(gdb) gcore
warning: target file /proc/.../cmdline contained unexpected null characters
The reason is that cmdline is read with target_fileio_read_stralloc(),
which warns on seeing null characters. However, it's perfectly valid
for cmdline to contain \0s, so switch to target_fileio_read_alloc().
Approved-By: Tom Tromey <tom@tromey.com>
Diffstat (limited to 'gdb/compile/compile-object-run.h')
0 files changed, 0 insertions, 0 deletions