Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: Isn't it OK to drop 'set write'?
Date: Mon, 03 Aug 2015 18:11:00 -0000	[thread overview]
Message-ID: <20150803181146.GA4674@adacore.com> (raw)
In-Reply-To: <20150726204905.GA18543@host1.jankratochvil.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


      parent reply	other threads:[~2015-08-03 18:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-26 20:49 Jan Kratochvil
2015-07-28 17:51 ` Doug Evans
2015-07-28 18:17   ` Jan Kratochvil
2015-08-03 18:11 ` Joel Brobecker [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150803181146.GA4674@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox