[gdb, hurd] Avoid using 'PATH_MAX' in 'gdb/remote.c'

..., which is not defined in GNU/Hurd systems, and so commit
94585166df "Extended-remote follow-exec" caused:

    [...]/gdb/remote.c: In member function 'void remote_target::remote_parse_stop_reply(const char*, stop_reply*)':
    [...]/gdb/remote.c:7343:22: error: 'PATH_MAX' was not declared in this scope
            char pathname[PATH_MAX];
                          ^~~~~~~~

	gdb/
	* remote.c (remote_target::remote_parse_stop_reply): Avoid using
	'PATH_MAX'.
This commit is contained in:
Thomas Schwinge 2017-02-17 16:45:01 +00:00
parent 8071c5ce78
commit b671c7fb21
2 changed files with 10 additions and 2 deletions

View File

@ -1,3 +1,9 @@
2019-02-14 Thomas Schwinge <thomas@codesourcery.com>
Pedro Alves <palves@redhat.com>
* remote.c (remote_target::remote_parse_stop_reply): Avoid using
'PATH_MAX'.
2019-02-14 David Michael <fedora.dm0@gmail.com>
Samuel Thibault <samuel.thibault@gnu.org>
Thomas Schwinge <thomas@codesourcery.com>

View File

@ -7340,7 +7340,6 @@ Packet: '%s'\n"),
else if (strprefix (p, p1, "exec"))
{
ULONGEST ignored;
char pathname[PATH_MAX];
int pathlen;
/* Determine the length of the execd pathname. */
@ -7349,11 +7348,14 @@ Packet: '%s'\n"),
/* Save the pathname for event reporting and for
the next run command. */
char *pathname = (char *) xmalloc (pathlen + 1);
struct cleanup *old_chain = make_cleanup (xfree, pathname);
hex2bin (p1, (gdb_byte *) pathname, pathlen);
pathname[pathlen] = '\0';
discard_cleanups (old_chain);
/* This is freed during event handling. */
event->ws.value.execd_pathname = xstrdup (pathname);
event->ws.value.execd_pathname = pathname;
event->ws.kind = TARGET_WAITKIND_EXECD;
/* Skip the registers included in this packet, since