Hi.
When you run gitk from a git repository on Windows it starts up and
starts updating its 'Row X/Y' output labels. This lasts for a few
seconds but if you terminate the application before this updating is
complete you get a Windows message stating:
'Wish Application has encountered a problem and needs to close. We
are sorry for the inconvenience.'
and the standard 'Send Error Report'/'Don't Send' buttons.
Hope this helps.
Best regards,
Jurko Gospodnetić
Hi.
When you run gitk from a git repository on Windows it starts up and
starts updating its 'Row X/Y' output labels. This lasts for a few
seconds but if you terminate the application before this updating is
complete you get a Windows message stating:
'Wish Application has encountered a problem and needs to close. We
are sorry for the inconvenience.'
and the standard 'Send Error Report'/'Don't Send' buttons.
Hope this helps.
Best regards,
Jurko Gospodnetić
Though I can't find the relevant commit at the moment
I believe that this is one already fixed in the latest
from git://repo.or.cz/git/mingw/4msysgit.git.
- Eric
When you run gitk from a git repository on Windows it starts up and
starts updating its 'Row X/Y' output labels. This lasts for a few
seconds but if you terminate the application before this updating is
complete you get a Windows message stating:
'Wish Application has encountered a problem and needs to close. We
are sorry for the inconvenience.'
and the standard 'Send Error Report'/'Don't Send' buttons.
Hope this helps.
Best regards,
Jurko Gospodnetić
Though I can't find the relevant commit at the moment
I believe that this is one already fixed in the latest
from git://repo.or.cz/git/mingw/4msysgit.git.
I don't think so. The error Jurko reported might be the same error
that was reported earlier and filed as issue 125:
http://code.google.com/p/msysgit/issues/detail?id=125
I don't think the problem is Windows-specific. At least on Mac I am
seeing similar problems. When I hit CTRL-q while gitk is still reading
the commits, it crashes with as segfault.
Steffen
I don't think the problem is Windows-specific. At least on Mac I am
seeing similar problems. When I hit CTRL-q while gitk is still reading
the commits, it crashes with as segfault.
Steffen
I also agree that it easily could be a generic problem.
But the fact remains that it used to reliably crash on me,
and no longer does with more recent source.
But I still can't find a relevant commit, which makes me
feel like I'm a) still a complete git newbie, or b) imagining
the whole thing.
- Eric
On Mon, Jul 28, 2008 at 09:18:35PM +0200, Steffen Prohaska wrote:
I don't think the problem is Windows-specific. At least on Mac I am
seeing similar problems. When I hit CTRL-q while gitk is still reading
the commits, it crashes with as segfault.
On Linux, when I hit CTRL-q (after a few attempts), I got this:
invalid command name ".tf.histframe.pwclist.canv"
while executing
"$canv yview"
(procedure "drawvisible" line 5)
invoked from within
"drawvisible"
(procedure "layoutmore" line 14)
invoked from within
"layoutmore"
(procedure "chewcommits" line 5)
invoked from within
"chewcommits"
("eval" body line 1)
invoked from within
"eval $script"
(procedure "dorunq" line 9)
invoked from within
"dorunq"
("after" script)
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 8 (X_MapWindow)
Resource id in failed request: 0x0
Serial number of failed request: 2453
Current serial number in output stream: 2456
Dmitry