From: "Tilo Schwarz" <tilo@tilo-schwarz.de>
To: "Jonas Fonseca" <jonas.fonseca@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] tig-0.14
Date: Sat, 21 Feb 2009 18:35:36 +0100 [thread overview]
Message-ID: <op.uppptmu7a8ed4e@dellschleppa> (raw)
In-Reply-To: <2c6b72b30902201535q2466b8fbtce746a5263ebf320@mail.gmail.com>
On Sat, 21 Feb 2009 00:35:59 +0100, Jonas Fonseca
<jonas.fonseca@gmail.com> wrote:
[...]
> OK, I have added the begining structure for a branch view, bound to
> 'H' by default. It does not support any actions besides refreshing and
> viewing the branch history. So there is still some work to achieve the
> easy access to branch commands.
That's really nice!
>> BTW, is the git list the right list to discuss bugs / patches for tig?
>
> Yes please.
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
next prev parent reply other threads:[~2009-02-21 17:37 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 20:44 [ANNOUNCE] tig-0.14 Jonas Fonseca
2009-02-06 10:49 ` bill lam
2009-02-06 14:29 ` Jonas Fonseca
2009-02-06 15:25 ` Sitaram Chamarty
2009-02-08 10:07 ` Jonas Fonseca
2009-02-11 16:05 ` showing SHA1 of parent commit in tig [was " Sitaram Chamarty
2009-02-12 1:19 ` Jonas Fonseca
2009-02-12 3:28 ` Sitaram Chamarty
2009-02-06 19:15 ` Jeff King
2009-02-06 22:10 ` Jonas Fonseca
2009-02-06 22:53 ` Jakub Narebski
2009-02-08 10:13 ` Jonas Fonseca
2009-02-07 7:10 ` Jeff King
2009-02-07 7:28 ` Junio C Hamano
2009-02-07 8:55 ` david
2009-02-08 10:47 ` Jonas Fonseca
2009-02-08 10:55 ` Jonas Fonseca
2009-02-08 11:06 ` Jeff King
2009-02-08 11:52 ` Jonas Fonseca
2009-02-07 11:26 ` Jeff King
2009-02-08 10:31 ` Jonas Fonseca
2009-02-08 11:00 ` Jeff King
2009-02-08 11:49 ` Jonas Fonseca
2009-02-07 2:48 ` Mikael Magnusson
2009-02-09 22:07 ` Peter Baumann
2009-02-09 22:22 ` Jeff King
2009-02-09 22:30 ` Peter Baumann
2009-02-10 18:42 ` Jonas Fonseca
2009-02-10 21:23 ` Jari Aalto
2009-02-10 13:29 ` Ted Pavlic
2009-02-10 18:29 ` Jonas Fonseca
2009-02-10 19:07 ` Brian Gernhardt
2009-02-10 19:29 ` Stefan Karpinski
2009-02-10 20:41 ` Jonas Fonseca
2009-02-10 20:49 ` Brian Gernhardt
2009-02-10 21:13 ` Jonas Fonseca
2009-02-10 21:18 ` Brian Gernhardt
2009-02-11 14:06 ` Ted Pavlic
2009-02-12 1:30 ` Jonas Fonseca
2009-02-11 14:19 ` Ted Pavlic
2009-02-20 17:24 ` Ted Pavlic
2009-02-20 18:34 ` Jonas Fonseca
2009-02-20 20:36 ` Ted Pavlic
2009-02-20 23:31 ` Jonas Fonseca
2009-02-25 21:54 ` Jonas Fonseca
2009-02-11 14:03 ` Ted Pavlic
2009-02-11 14:12 ` Ted Pavlic
2009-02-11 17:47 ` Ted Pavlic
2009-02-12 1:08 ` Jonas Fonseca
2009-02-12 21:48 ` Tilo Schwarz
2009-02-12 22:24 ` Jonas Fonseca
2009-02-12 23:14 ` Tilo Schwarz
2009-02-15 23:47 ` Jonas Fonseca
2009-02-16 1:33 ` Sitaram Chamarty
2009-02-16 12:10 ` Jonas Fonseca
2009-02-16 15:14 ` Sitaram Chamarty
2009-02-16 15:25 ` Thomas Adam
2009-02-16 19:52 ` Jonas Fonseca
2009-02-17 7:47 ` Marco Costalba
2009-02-16 21:12 ` Tilo Schwarz
2009-02-20 23:35 ` Jonas Fonseca
2009-02-21 17:35 ` Tilo Schwarz [this message]
2009-02-21 17:41 ` Jonas Fonseca
2009-02-21 20:18 ` Tilo Schwarz
2009-02-16 21:55 ` Tilo Schwarz
2009-02-13 2:31 ` bill lam
2009-02-13 23:57 ` Jonas Fonseca
2009-02-14 3:31 ` bill lam
2009-02-15 23:22 ` Jonas Fonseca
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=op.uppptmu7a8ed4e@dellschleppa \
--to=tilo@tilo-schwarz.de \
--cc=git@vger.kernel.org \
--cc=jonas.fonseca@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).