[gdb, hurd] Avoid using 'PATH_MAX' in 'gdb/remote.c'
authorThomas Schwinge <thomas@codesourcery.com>
Fri, 17 Feb 2017 16:45:01 +0000 (16:45 +0000)
committerThomas Schwinge <thomas@codesourcery.com>
Thu, 14 Feb 2019 16:40:19 +0000 (17:40 +0100)
commitb671c7fb21306ce125717a44c30a71686bd24db1
tree82be0213d6a8af860e98512111b7b0b06190d078
parent8071c5ce78245eff43f9977a7c3ff8328f7486da
[gdb, hurd] Avoid using 'PATH_MAX' in 'gdb/remote.c'

..., which is not defined in GNU/Hurd systems, and so commit
94585166dfea8232c248044f9f4b1c217dc4ac2e "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'.
gdb/ChangeLog
gdb/remote.c