Git development
 help / color / mirror / Atom feed
From: Martin Waitz <tali@admingilde.org>
To: git@vger.kernel.org
Subject: SEGV in git-apply
Date: Sat, 20 Jan 2007 02:48:52 +0100	[thread overview]
Message-ID: <20070120014851.GF5231@admingilde.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]

hoi :)

I just hit this bug in git-apply, while executing it in a subdirectory.
At the moment I am using some mixture of next and some own changes
(mostly submodule support, should not affect this bug).

I am afraid that I don't have the time to fix it myself atm, so I am simply
attaching the backtrace here:

Program received signal SIGSEGV, Segmentation fault.
0x080500fa in apply_patch (fd=5, filename=0xbf821b4d "/tmp/404241.patch",
    inaccurate_eof=<value optimized out>) at builtin-apply.c:2504
2504                    if (pathlen <= prefix_length ||
(gdb) bt
#0  0x080500fa in apply_patch (fd=5, filename=0xbf821b4d "/tmp/404241.patch",
    inaccurate_eof=<value optimized out>) at builtin-apply.c:2504
#1  0x0805147a in cmd_apply (argc=3, argv=0xbf8201e4, prefix=0x80e75c6 "src/")
    at builtin-apply.c:2719
#2  0x0804ab55 in handle_internal_command (argc=3, argv=0xbf8201e4,
    envp=<value optimized out>) at git.c:304
#3  0x0804b1f8 in main (argc=3, argv=Cannot access memory at address 0x8
) at git.c:341


-- 
Martin Waitz

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2007-01-20  1:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-20  1:48 Martin Waitz [this message]
2007-01-20  2:14 ` SEGV in git-apply Johannes Schindelin
2007-01-20 18:36   ` Martin Waitz
2007-01-21  1:17     ` [PATCH] apply --cached: fix crash in subdirectory Johannes Schindelin
2007-01-21 14:40       ` Martin Waitz
2007-01-21 16:47       ` Rogan Dawes
2007-01-21 18:03         ` 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=20070120014851.GF5231@admingilde.org \
    --to=tali@admingilde.org \
    --cc=git@vger.kernel.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