This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v2] Fix logic in exec_file_locate_attach
- From: Pedro Alves <palves at redhat dot com>
- To: Gary Benson <gbenson at redhat dot com>, Luis Machado <lgustavo at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Tue, 23 Feb 2016 11:43:47 +0000
- Subject: Re: [PATCH v2] Fix logic in exec_file_locate_attach
- Authentication-results: sourceware.org; auth=none
- References: <56C736ED dot 9040505 at codesourcery dot com> <20160222104034 dot GA31531 at blade dot nx> <56CAF2E3 dot 7050607 at codesourcery dot com> <20160222135109 dot GA2256 at blade dot nx> <56CB8506 dot 3010602 at codesourcery dot com> <56CB9095 dot 9090908 at codesourcery dot com> <56CB9304 dot 9020408 at redhat dot com> <56CBA220 dot 3000709 at codesourcery dot com> <56CBA443 dot 6010106 at redhat dot com> <56CBA4BA dot 7050905 at codesourcery dot com> <20160223112721 dot GA22369 at blade dot nx>
On 02/23/2016 11:27 AM, Gary Benson wrote:
> I hadn't considered user interrupts.
But there's nothing about user interrupts in either of:
https://sourceware.org/ml/gdb-patches/2016-02/msg00511.html
or:
https://sourceware.org/ml/gdb-patches/2016-02/msg00671.html
That is about gdb managing to figure out the file name of the running
program, but then trying to open the file, and that failing and throwing.
- The original failure Luis found was triggered when the file didn't
exist at all in the sysroot.
- The failure I shown in the urls above is that the file exists in the
sysroot but is unreadable.
These are both basically the same problem, except the latter is easier
to reproduce.
So trying to open the file _in_ the sysroot may fail and throw, but
that should not abort the remote connection, nor an "attach" (command)
sequence, both of which use the same exec_file_locate_attach routine
-- the remote connection case is really basically doing an attach.
Thanks,
Pedro Alves