From: Pierre Habouzit <madcoder@debian.org>
To: Shun Kei Leung <kevinlsk@gmail.com>
Cc: git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: git-fast-import crashes
Date: Tue, 16 Oct 2007 10:04:05 +0200 [thread overview]
Message-ID: <20071016080405.GC6919@artemis.corp> (raw)
In-Reply-To: <e66701d40710160101x5c697a6fmeecea4c81dfd9972@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]
On Tue, Oct 16, 2007 at 08:01:18AM +0000, Shun Kei Leung wrote:
> > What I _really_ need is that you run your test into valgrind (the easy
> > way is to rename git-fast-import into git-fast-import.bin, and make
> > git-fast-import be a shell-script doing:
> ....
>
> valgrind is not yet ported to Mac OS X, sadly enough.
hmmm I see. hmmm isn't there _any_ chance that you can have access to
a linux box to see if that fails in the same conditions ? I mean I
believe qemu (or virtual pc or …) on your macos would be just fine.
But this realloc() that returns 0xd looks fishy. I would be tempted to
think of a stack corruption, but the frame just before still looks
correct so I'm confused. And valgrind is definitely the tool to use for
stack smashing and other memory related corruptions :/
Using gcc -Wstack-protector may also help.
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-10-16 8:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 9:42 git-fast-import crashes Shun Kei Leung
2007-10-13 3:29 ` Shawn O. Pearce
2007-10-13 3:34 ` Shawn O. Pearce
2007-10-13 7:36 ` Pierre Habouzit
2007-10-13 7:50 ` Pierre Habouzit
2007-10-15 4:53 ` Shun Kei Leung
2007-10-15 7:33 ` Pierre Habouzit
2007-10-15 8:19 ` Shun Kei Leung
2007-10-16 7:13 ` Shun Kei Leung
2007-10-16 7:46 ` Pierre Habouzit
2007-10-16 8:01 ` Shun Kei Leung
2007-10-16 8:04 ` Pierre Habouzit [this message]
2007-10-13 12:58 ` Johannes Schindelin
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=20071016080405.GC6919@artemis.corp \
--to=madcoder@debian.org \
--cc=git@vger.kernel.org \
--cc=kevinlsk@gmail.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 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.