This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Make only user-specified executable filenames sticky
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: Gary Benson <gbenson at redhat dot com>, Doug Evans <dje at google dot com>, gdb-patches <gdb-patches at sourceware dot org>, Philippe Waroquiers <philippe dot waroquiers at skynet dot be>
- Date: Wed, 3 Jun 2015 10:23:39 -0700
- Subject: Re: [PATCH] Make only user-specified executable filenames sticky
- Authentication-results: sourceware.org; auth=none
- References: <20150505151448 dot GA1417 at blade dot nx> <1430907977-30605-1-git-send-email-gbenson at redhat dot com> <CADPb22SDB9qV1BgP2JmCxsu-E8QXDj1SLnCjBjGWn+g+1M7V7A at mail dot gmail dot com> <5551D7AD dot 8080500 at redhat dot com> <CADPb22R8yoX8M7Ws0D4QFDOqK1cgdveNsrdrJwp_=SuCH64qcw at mail dot gmail dot com> <20150513075456 dot GA3730 at blade dot nx> <5553157D dot 3060104 at redhat dot com>
> Though maybe we're trying to make gdb
> too smart, as in, some obscure cases things may go wrong,
> depending on program/binary and target you connect to,
> which is confusing.
After quickly going through the discussion, I tend to agree.
How about:
(1) Provide a way to recover the situation _after_ the "attach";
(2) Print a warning if the attach notices that the executable name
does not match the one given by the user, and include the
procedure for fixing it if the user made an error.
?
We could do this in two steps:
a. Push Gary's patch today, after having enhanced it to print
a warning when discrepancies are discovered;
b. Work on a way to achieve (1), and then enhance the warning
to mention how to resolve this issue.
That way, we could have (a) in time for 7.10, and work for (b)
without delaying 7.10. Whether (b) makes it to 7.10 will then
depend on how quickly we find a solution, but it's OK IMO for it
to provide that in a later release.
--
Joel