All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: kusmabite@gmail.com, Philip Oakley <philipoakley@iee.org>, "Koch\,
	Rick \(Subcontractor\)" <Rick.Koch@tbe.com>,
	Git List <git@vger.kernel.org>
Subject: Re: CPPCheck found 24 high risk bugs in Git v.1.8.3.4
Date: Tue, 20 Aug 2013 16:45:10 -0700	[thread overview]
Message-ID: <xmqqd2p8udtl.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <87y57wnf03.fsf@igel.home> (Andreas Schwab's message of "Wed, 21 Aug 2013 01:01:32 +0200")

Andreas Schwab <schwab@linux-m68k.org> writes:

> Erik Faye-Lund <kusmabite@gmail.com> writes:
>
>> I don't see how it's undefined. It's using the memory that 'pos'
>> *points to* that is undefined, no? The difference between 'pos' and
>> 'str' should still be the same, it's not like realloc somehow
>> magically updates 'pos'...
>
> It does.  Think of segmented architectures, where freeing a pointer
> invalidates its segment, so that even loading the value of the pointer
> traps.  Probably no such architecture is in use any more, though.

I love seeing that we have somebody who knows and can explain these
dark corners of ANSI C standard ;-)

  reply	other threads:[~2013-08-20 23:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-19 17:09 CPPCheck found 24 high risk bugs in Git v.1.8.3.4 Koch, Rick (Subcontractor)
2013-08-19 20:03 ` Philip Oakley
2013-08-19 20:40   ` Jeff King
2013-08-19 20:46     ` Junio C Hamano
2013-08-19 20:52       ` Johan Herland
     [not found]   ` <85C8141E5DAD94428A121F706995A31F010F116FDADE@MX1.net.tbe.com>
2013-08-19 21:46     ` Philip Oakley
2013-08-23 19:51       ` CPPCheck found 24 high risk bugs in Git v.1.8.3.4 (fetch.c L588) Philip Oakley
2013-08-19 22:55   ` CPPCheck found 24 high risk bugs in Git v.1.8.3.4 Philip Oakley
2013-08-19 23:15     ` Erik Faye-Lund
2013-08-20 14:33       ` Jeff King
2013-08-20 18:44       ` Andreas Schwab
2013-08-20 20:34         ` René Scharfe
2013-08-20 22:28           ` Erik Faye-Lund
2013-08-20 22:26         ` Erik Faye-Lund
2013-08-20 23:01           ` Andreas Schwab
2013-08-20 23:45             ` Junio C Hamano [this message]
2013-08-21  0:01             ` Erik Faye-Lund
2013-08-19 21:36 ` Stefan Beller

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=xmqqd2p8udtl.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=Rick.Koch@tbe.com \
    --cc=git@vger.kernel.org \
    --cc=kusmabite@gmail.com \
    --cc=philipoakley@iee.org \
    --cc=schwab@linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.