This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Copy .py files to remote host
- From: Doug Evans <dje at google dot com>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: gdb-patches <gdb-patches at sourceware dot org>
- Date: Tue, 12 Aug 2014 22:50:35 -0700
- Subject: Re: [PATCH] Copy .py files to remote host
- Authentication-results: sourceware.org; auth=none
- References: <1407849103-16521-1-git-send-email-yao at codesourcery dot com> <21482 dot 19388 dot 251662 dot 22760 at ruffy dot mtv dot corp dot google dot com> <53EAB6C4 dot 40406 at codesourcery dot com> <CADPb22TN7qPfFWb36JmUAMPFhEvjF=+FDM09pNo2w_om1N0S-A at mail dot gmail dot com>
On Tue, Aug 12, 2014 at 8:09 PM, Doug Evans <dje@google.com> wrote:
> On Tue, Aug 12, 2014 at 5:52 PM, Yao Qi <yao@codesourcery.com> wrote:
>> On 08/13/2014 01:15 AM, Doug Evans wrote:
>>> I still have an outstanding question on this topic,
>>> and before this gets checked in I'd like to get it resolved.
>>> Do we delete other files downloaded to the remote target?
>>
>> Yes, at least shared libs downloaded to target are cleaned up.
>> In lib/gdb.exp, there is a list cleanfiles, to record the files
>> downloaded to target, and in gdb_finish, remove files in this list.
>
> Yeah, we keep track of files downloaded to the target.
> Can we do something similar for the host?
Though I should also say every time I've used a system that tries to
clean up after itself too much I generally grow to dislike it -
debugging failures gets harder because the files are gone.
If possible, I'd rather do a cleanup of the previous run beforehand
and just leave the results lying around afterwards (and often it's
easy because something simple like rm -rf $something is all that's
needed).