On Sat, 21 Feb 2009 00:35:59 +0100, Jonas Fonseca <jonas.fonseca@gmail.com> wrote: [...]That's really nice! Ok, here we go ;-). I can trigger a SIGSEGV in da8b99da8f4dc5512c23154ec6c0aa7d3c313555 like this, using the tig repo itself: - Start ./tig --all - Enter the new branch view pressing 'H' - Add a new branch foo using git checkout -b foo on some console or in tig using ':checkout -b foo' - Press F5 in the branch view to reload - Move cursor on the new branch foo - Press ENTER Then I get a SIGSEGV in line 6150 if (ref->head) (gdb) print *ref Cannot access memory at address 0x2d676974 #0 0x08056427 in main_draw (view=0x8060500, line=0x9b61638, lineno=0) at tig.c:6150 #1 0x0804d19d in draw_view_line (view=0x8060500, lineno=0) at tig.c:2111 #2 0x0804d269 in redraw_view_from (view=0x8060500, lineno=0) at tig.c:2141 #3 0x0804d2bf in redraw_view (view=0x8060500) at tig.c:2152 #4 0x0804f70b in open_view (prev=0x8062fa8, request=REQ_VIEW_MAIN, flags=OPEN_SPLIT) at tig.c:3055 #5 0x08053241 in branch_request (view=0x8062fa8, request=REQ_ENTER, line=0x9b6b038) at tig.c:4783 #6 0x0804f9df in view_driver (view=0x8062fa8, request=REQ_ENTER) at tig.c:3142 #7 0x080594a3 in main (argc=Cannot access memory at address 0x3 I tried to track this down, but was not successful yet (having seen tig.c the first time today). I looked in get_refs and read_ref, but couldn't nail it down up to now. It feels, as if the refresh does find and update the new branch foo, but the corresponding commit->refs are not properly updated (just guessing). Best regards & thank you for tig! Tilo -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Greg KH | Og dreams of kernels |
| Jens Axboe | [PATCH 31/33] Fusion: sg chaining support |
| Arnd Bergmann | Re: finding your own dead "CONFIG_" variables |
| Mark Brown | [PATCH 2/2] Subject: natsemi: Allow users to disable workaround for DspCfg reset |
| Tony Breeds | [LGUEST] Look in object dir for .config |
git: | |
| Brian Downing | Re: Git in a Nutshell guide |
