From: "Randall S. Becker" <email@example.com> To: "'git mailing list'" <firstname.lastname@example.org> Subject: RE: [BUG] Weird breakages in t1450 #2 on NonStop Date: Thu, 11 Jan 2018 16:39:04 -0500 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> On January 11, 2018 9:46 AM, I wrote: > This one has me scratching my head: > > The object file name being reported below in t1450, subtest 2 is corrupt, but I > can't figure out why the script might be generating this condition - there's > nothing apparent, but it looks like the git commit -m C step is reporting or > using a bad name. This breakage was not present in 2.8.5 (now at 7234152 > (2.13.5) and is persistent (i.e. always happens). This is the only test in all of > git where I have observed this particular situation. > Adding set -x to test_commit is unrevealing. The git fsck in this test is never > executed because the test_commit fails with a non-zero git commit > completion code. There is no rn---- (actual r n 252 252 252 252) in the objects > directory - even the 'rn' does not correspond to anything.. I am suspecting an > unterminated string that ran into freed memory somewhere, but that's > speculative. Does anyone recall fixing this one at or near dfe46c5ce6e68d682f80f9874f0eb107e9fee797? There was a rewrite of sha1_file.c including link_alt_odb_entry where I am finding memory corruptions. I think I'm chasing something that was already fixed some time after 2.13.5 but the common parent to where I am is pretty far back compared to master. Thanks, Randall -- Brief whoami: NonStop developer since approximately NonStop(211288444200000000) UNIX developer since approximately 421664400 -- In my real life, I talk too much.
next prev parent reply other threads:[~2018-01-11 21:39 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-01-11 14:45 Randall S. Becker 2018-01-11 21:39 ` Randall S. Becker [this message] 2018-01-12 14:39 ` Jeff King 2018-01-12 15:47 ` Randall S. Becker
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 List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com' \ --firstname.lastname@example.org \ --email@example.com \ --subject='RE: [BUG] Weird breakages in t1450 #2 on NonStop' \ /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
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git 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).