From: "Joachim Schmitz" <jojo@schmitz-digital.de>
To: "'Johannes Sixt'" <j6t@kdbg.org>
Cc: "'Brandon Casey'" <drafnel@gmail.com>,
"'Junio C Hamano'" <gitster@pobox.com>,
"'Shawn Pearce'" <spearce@spearce.org>, <git@vger.kernel.org>,
<rsbecker@nexbridge.com>
Subject: RE: Porting git to HP NonStop
Date: Wed, 22 Aug 2012 20:18:14 +0200 [thread overview]
Message-ID: <004001cd8092$7f9e6540$7edb2fc0$@schmitz-digital.de> (raw)
In-Reply-To: <50352053.609@kdbg.org>
> -----Original Message-----
> From: Johannes Sixt [mailto:j6t@kdbg.org]
> Sent: Wednesday, August 22, 2012 8:09 PM
> To: Joachim Schmitz
> Cc: 'Brandon Casey'; 'Junio C Hamano'; 'Shawn Pearce'; git@vger.kernel.org;
> rsbecker@nexbridge.com
> Subject: Re: Porting git to HP NonStop
>
> Am 22.08.2012 20:02, schrieb Joachim Schmitz:
> >> From: Johannes Sixt [mailto:j6t@kdbg.org] Don't use x* wrappers in
> >> the compat layer, at least not those that allocate
> >> memory: They behave unpredictably due to try_to_free_routine and may
> >> lead to recursive invocations.
> >
> > I was just following orders ;-)
> > What about the other proposal, xmemdupz? Same story I guess?
>
> xmemdupz calls xmalloc, so, yes, same story.
So back to my original patch, using strdup, check the return value, etc.
Bye, Jojo
next prev parent reply other threads:[~2012-08-22 18:18 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 15:04 Porting git to HP NonStop Joachim Schmitz
2012-08-10 16:27 ` Shawn Pearce
2012-08-10 17:32 ` Joachim Schmitz
2012-08-10 17:38 ` Shawn Pearce
2012-08-19 8:57 ` Joachim Schmitz
2012-08-19 17:23 ` Junio C Hamano
2012-08-20 10:22 ` Joachim Schmitz
2012-08-20 14:41 ` Junio C Hamano
2012-08-20 16:09 ` Joachim Schmitz
2012-08-20 16:53 ` Junio C Hamano
2012-08-22 16:30 ` Joachim Schmitz
2012-08-22 17:00 ` Brandon Casey
2012-08-22 17:13 ` Brandon Casey
2012-08-22 17:18 ` Joachim Schmitz
2012-08-22 17:23 ` Brandon Casey
2012-08-22 17:30 ` Joachim Schmitz
2012-08-22 17:30 ` Junio C Hamano
2012-08-22 18:01 ` Joachim Schmitz
2012-08-22 18:24 ` Junio C Hamano
2012-08-22 18:52 ` Joachim Schmitz
2012-08-22 17:41 ` Johannes Sixt
2012-08-22 18:02 ` Joachim Schmitz
2012-08-22 18:09 ` Johannes Sixt
2012-08-22 18:18 ` Joachim Schmitz [this message]
2012-08-22 18:09 ` Brandon Casey
2012-08-22 18:24 ` Brandon Casey
2012-08-22 18:33 ` Junio C Hamano
2012-08-22 18:38 ` Brandon Casey
2012-08-22 20:18 ` Joachim Schmitz
2012-08-22 20:49 ` Junio C Hamano
2012-08-22 21:05 ` Joachim Schmitz
2012-08-22 21:12 ` Junio C Hamano
2012-08-22 21:22 ` Joachim Schmitz
2012-08-22 21:54 ` Junio C Hamano
2012-08-22 18:26 ` Junio C Hamano
2012-08-10 20:08 ` Joachim Schmitz
2012-08-11 8:20 ` Johannes Sixt
2012-08-14 7:05 ` Joachim Schmitz
2012-08-14 14:56 ` Junio C Hamano
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='004001cd8092$7f9e6540$7edb2fc0$@schmitz-digital.de' \
--to=jojo@schmitz-digital.de \
--cc=drafnel@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=rsbecker@nexbridge.com \
--cc=spearce@spearce.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 NNTP newsgroup(s).