From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Christopher Faylor" <me@cgf.cx>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: cygwin: push/pull takes very long time
Date: Fri, 3 Mar 2006 10:10:25 +0100 [thread overview]
Message-ID: <81b0412b0603030110x73f080ao6a5798e339aa6355@mail.gmail.com> (raw)
In-Reply-To: <20060303002806.GB7497@trixie.casa.cgf.cx>
On 3/3/06, Christopher Faylor <me@cgf.cx> wrote:
> On Thu, Mar 02, 2006 at 10:54:08PM +0100, Alex Riesen wrote:
> >Alex Riesen, Thu, Mar 02, 2006 18:09:23 +0100:
> >>I'll cleanup the profiling code and send it as well soon (I had to
> >>instrument x*alloc).
> >
> >This is not exactly the same. It counts free as well, even if that is
> >not really interesting - there are places were there is more frees than
> >allocs. Probably something missed or a result coming from libc.
> >
> >Also it is _not_ the code I used for windows. I had to have a global
> >variable for argv[0], which needs modification of all main()s, which
> >gets too easily out of sync.
>
> I wasn't following this discussion closely so maybe this is useless
> information, but for Cygwin you can either use the undocumented global
> __argv or you can use /proc/cmdline. /proc/self/cmdline is going to be
> pretty slow, however.
Oh, thanks. The speed is of no problem here: it's in atexit callback.
> It looks like pure Windows console apps define _argv in stdlib.h also
> but I've never used this and don't know if it is what it looks like.
It works as usual argv. I used "char **__argv", got the message from linker:
Info: resolving ___argv by linking to __imp____argv (auto-import)
which I almost expected.
prev parent reply other threads:[~2006-03-03 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 13:26 cygwin: push/pull takes very long time Alex Riesen
2006-03-02 17:09 ` Alex Riesen
2006-03-02 21:54 ` Alex Riesen
2006-03-03 0:28 ` Christopher Faylor
2006-03-03 9:10 ` Alex Riesen [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=81b0412b0603030110x73f080ao6a5798e339aa6355@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=me@cgf.cx \
/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).