git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Steffen Prohaska <prohaska@zib.de>
To: Eric Raible <raible@gmail.com>
Cc: git@vger.kernel.org
Subject: gitk crashes when quitting gitk while it is is reading commits (was Re: gitk crashing on Windows.)
Date: Mon, 28 Jul 2008 21:18:35 +0200	[thread overview]
Message-ID: <E7C7B8BA-6050-40DE-917C-200EAE9CA6E8@zib.de> (raw)
In-Reply-To: <loom.20080728T162025-946@post.gmane.org>


On Jul 28, 2008, at 6:29 PM, Eric Raible wrote:

> Jurko Gospodnetić <jurko.gospodnetic <at> docte.hr> writes:
>
>>   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

  reply	other threads:[~2008-07-28 19:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28 14:58 gitk crashing on Windows Jurko Gospodnetić
2008-07-28 16:29 ` Eric Raible
2008-07-28 19:18   ` Steffen Prohaska [this message]
2008-07-28 20:31     ` gitk crashes when quitting gitk while it is is reading commits (was Re: gitk crashing on Windows.) Eric Raible
2008-07-29 13:15     ` Dmitry Potapov

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E7C7B8BA-6050-40DE-917C-200EAE9CA6E8@zib.de \
    --to=prohaska@zib.de \
    --cc=git@vger.kernel.org \
    --cc=raible@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).