git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [bug] Segfault in git rev-list --first-parent --bisect

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 23, 2008, 04:51 UTC
Message-ID
<7vhc9c49ls.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<32541b130808222020v146e015dm8a98a005ad3e76a7@mail.gmail.com>
"Avery Pennarun" <apenwarr@gmail.com> writes:
Show 9 quoted lines
> I've tried the following command sequence in git 1.5.6, 1.6.0,
> 1.6.0.8.ga578a, and 1.6.0.90.g436ed.
>
>     $ git clone git://repo.or.cz/versaplex.git
>     $ cd versaplex.git
>     $ git rev-list --first-parent --bisect 5109c91 ^d798a2bfe094
>     Segmentation fault
>
> Removing either the --first-parent or the --bisect makes the segfault go away.

Don't use them both then. I do not think --bisect pays any attention to the usual revision traversal rules.

Previous: Avery PennarunNext: Junio C Hamano
Message 2 of 4 in “[bug] Segfault in git rev-list --first-parent --bisect”
  1. Avery PennarunAug 23, 2008
  2. Junio C HamanoAug 23, 2008
  3. Junio C HamanoAug 23, 2008
  4. Junio C HamanoAug 23, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.