public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "pedro at palves dot net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/18168] "set write on" or "--write" corrupt the binary file - 7.9 regression
Date: Fri, 13 May 2022 10:08:07 +0000	[thread overview]
Message-ID: <bug-18168-4717-Vb5nkff0L7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18168-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=18168

Pedro Alves <pedro at palves dot net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
                 CC|                            |pedro at palves dot net

--- Comment #4 from Pedro Alves <pedro at palves dot net> ---
This has been fixed since, probably by:

commit db72737006fc383cb8838bf7f3dc8e641e60c38f
Author:     Jozef Lawrynowicz <jozef.l@mittosystems.com>
AuthorDate: Tue Sep 11 22:56:36 2018 +0100
Commit:     Tom Tromey <tom@tromey.com>
CommitDate: Mon Sep 24 06:20:17 2018 -0600

    Fix PR gdb/20948: --write option to GDB causes segmentation fault

This commit adds a testcase that would fail if GDB still corrupted the binary:

commit 169692ce6c0fa21c4648d2862cb2bb94012a1cd9
Author:     Pedro Alves <pedro@palves.net>
AuthorDate: Wed May 11 14:20:15 2022 +0100
Commit:     Pedro Alves <pedro@palves.net>
CommitDate: Fri May 13 10:56:05 2022 +0100

    Fix "gdb --write" with core files


Closing.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2022-05-13 10:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 16:52 [Bug gdb/18168] New: "set write on" or "--write" corrupt the binary file mail at cristos dot x25.pl
2015-03-26 18:10 ` [Bug gdb/18168] " mail at cristos dot x25.pl
2015-03-26 18:43 ` mail at cristos dot x25.pl
2015-07-26 20:34 ` jan.kratochvil at redhat dot com
2015-07-27 16:30 ` [Bug gdb/18168] "set write on" or "--write" corrupt the binary file - 7.9 regression jan.kratochvil at redhat dot com
2022-05-13 10:08 ` pedro at palves dot net [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=bug-18168-4717-Vb5nkff0L7@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).