All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bo Yang <struggleyb.nku@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org, Jens.Lehmann@web.de, trast@student.ethz.ch,
	gitster@pobox.com
Subject: Re: log -L crash (Re: [PATCH V5 13/17] Add parent rewriting to line history browser)
Date: Wed, 1 Sep 2010 22:47:11 +0800	[thread overview]
Message-ID: <AANLkTik2WgTkjH4nDs2QKSfb+rn4-QioGOeJZJ4NgN9t@mail.gmail.com> (raw)
In-Reply-To: <20100830171007.GC21441@burratino>

Hi Jonathan,

   Thanks a lot for providing such a detail valgrind trace output, I
will find out what happened to the code in this Friday, and give a fix
then. Thanks again for let me know it. Thanks!

On Tue, Aug 31, 2010 at 1:10 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Hi Bo et al,
>
> The following test fails (segfaults) for me.  It bisects to 83361f5
> (Add parent rewriting to line history browser, 2010-08-11).  Notes
> from --valgrind:
>
>        Invalid read of size 4
>           at assign_parents_range (line.c:1069)
>           by cmd_line_log_walk (line.c:1403)
>           by cmd_log (log.c:619)
>           by handle_internal_command (git.c:270)
>           by main (git.c:470)
>         Address 0x432a90c is 4 bytes inside a block of size 8 free'd
>           at free (vg_replace_malloc.c:366)
>           by assign_range_to_parent (line.c:964)
>           by assign_parents_range (line.c:1036)
>           by cmd_line_log_walk (line.c:1403)
>           by cmd_log (log.c:619)
>           by handle_internal_command (git.c:270)
>           by main (git.c:470)
>
>        Invalid read of size 4
>           at assign_parents_range (line.c:1041)
>           by cmd_line_log_walk (line.c:1403)
>           by cmd_log (log.c:619)
>           by handle_internal_command (git.c:270)
>           by main (git.c:470)
>         Address 0x0 is not stack'd, malloc'd or (recently) free'd
>
>        Process terminating with default action of signal 11 (SIGSEGV): dumping core
>         Access not within mapped region at address 0x0
>           at assign_parents_range (line.c:1041)
>           by cmd_line_log_walk (line.c:1403)
>           by cmd_log (log.c:619)
>           by handle_internal_command (git.c:270)
>           by main (git.c:470)
>         If you believe this happened as a result of a stack
>         overflow in your program's main thread (unlikely but
>         possible), you can try to increase the size of the
>         main thread stack using the --main-stacksize= flag.
>         The main thread stack size used in this run was 8388608.
>
> Ideas?
>
> diff --git a/t/t0011-crash.sh b/t/t0011-crash.sh
> index e69de29..5cb3ef3 100644
> --- a/t/t0011-crash.sh
> +++ b/t/t0011-crash.sh
> @@ -0,0 +1,11 @@
> +#!/bin/sh
> +
> +test_description=crash
> +. ./test-lib.sh
> +
> +test_expect_success "doesn't crash" '
> +       GIT_DIR="$TEST_DIRECTORY"/../.git \
> +               git log -L "/while (1) {/,/}/" git.c
> +'
> +
> +test_done
> --
>



-- 
Regards!
Bo
----------------------------
My blog: http://blog.morebits.org
Why Git: http://www.whygitisbetterthanx.com/

  reply	other threads:[~2010-09-01 14:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-11 15:03 [PATCH V5 00/17] Reroll a version 5 of this series Bo Yang
2010-08-11 15:03 ` [PATCH V5 01/17] parse-options: enhance STOP_AT_NON_OPTION Bo Yang
2010-08-11 15:03 ` [PATCH V5 02/17] parse-options: add two helper functions Bo Yang
2010-08-11 15:03 ` [PATCH V5 03/17] Add the basic data structure for line level history Bo Yang
2010-08-11 15:03 ` [PATCH V5 04/17] Refactor parse_loc Bo Yang
2010-08-11 15:03 ` [PATCH V5 05/17] Parse the -L options Bo Yang
2010-08-11 15:03 ` [PATCH V5 06/17] Export three functions from diff.c Bo Yang
2010-08-11 15:03 ` [PATCH V5 07/17] Add range clone functions Bo Yang
2010-08-11 15:03 ` [PATCH V5 08/17] map/take range to the parent of commits Bo Yang
2010-08-11 15:03 ` [PATCH V5 09/17] Print the line log Bo Yang
2010-08-11 15:03 ` [PATCH V5 10/17] Hook line history into cmd_log, ensuring a topo-ordered walk Bo Yang
2010-08-11 15:03 ` [PATCH V5 11/17] Make rewrite_parents public to other part of git Bo Yang
2010-08-11 15:03 ` [PATCH V5 12/17] Make graph_next_line external " Bo Yang
2010-08-11 15:03 ` [PATCH V5 13/17] Add parent rewriting to line history browser Bo Yang
2010-08-30 17:10   ` log -L crash (Re: [PATCH V5 13/17] Add parent rewriting to line history browser) Jonathan Nieder
2010-09-01 14:47     ` Bo Yang [this message]
2010-09-11 21:10     ` [PATCH] log -L: do not free parents lists we might need again Thomas Rast
2010-08-11 15:03 ` [PATCH V5 14/17] Add --graph prefix before line history output Bo Yang
2010-08-11 15:03 ` [PATCH V5 15/17] Add --full-line-diff option Bo Yang
2010-08-11 15:03 ` [PATCH V5 16/17] Add tests for line history browser Bo Yang
2010-08-12  1:25   ` Ævar Arnfjörð Bjarmason
2010-08-12 12:24     ` Bo Yang
2010-08-12 16:27       ` Ævar Arnfjörð Bjarmason
2010-08-12 20:37       ` Junio C Hamano
2010-08-12 21:06   ` Junio C Hamano
2010-08-11 15:03 ` [PATCH V5 17/17] Document " Bo Yang
2010-08-12  8:31 ` [PATCH V5 00/17] Reroll a version 5 of this series david
2010-08-12 17:23 ` 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=AANLkTik2WgTkjH4nDs2QKSfb+rn4-QioGOeJZJ4NgN9t@mail.gmail.com \
    --to=struggleyb.nku@gmail.com \
    --cc=Jens.Lehmann@web.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    --cc=trast@student.ethz.ch \
    /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.