This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Isn't it OK to drop 'set write'?
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: gdb at sourceware dot org
- Date: Mon, 3 Aug 2015 11:11:46 -0700
- Subject: Re: Isn't it OK to drop 'set write'?
- Authentication-results: sourceware.org; auth=none
- References: <20150726204905 dot GA18543 at host1 dot jankratochvil dot net>
> I cannot much imagine when it is useful. For updates of too big
> binaries there is gold incremental linking. Personally I have also
> never considered it safe enough to use it myself, hexedit is there if
> one needs to create a weird testfile.
On Tru64 (which we no longer support), thread support required writing
into inferior memory; so if you wanted thread support when debugging
a core file, you needed to set write on.
We have a couple of tests that set it unconditionally on all platforms,
and it seems to have no adverse effect. Beyond that, I'm not sure.
--
Joel