All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-parisc@vger.kernel.org
Subject: Re: Random crashes when calling git
Date: Mon, 31 Dec 2012 12:03:39 +0100	[thread overview]
Message-ID: <3563905.2dklDXemHT@donald.sf-tec.de> (raw)
In-Reply-To: <BLU0-SMTP552A5EEA5FEF5F4C363ADC97380@phx.gbl>

[-- Attachment #1: Type: text/plain, Size: 905 bytes --]

John David Anglin wrote:
> On 27-Dec-12, at 4:42 AM, Rolf Eike Beer wrote:
> > Any ideas?
> 
> Try running the test under gdb.  Git has branched to location 0 causing
> a page fault.  We need a backtrace(s) to learn something useful.  There
> may be multiple backtraces (info thread).

This did not lead anywhere. I tried running the test only with strace, but 
even that did not lead to any crash.

> Enable core dumps if not enabled.  Might find something useful by
> examining it (gdb -c core /usr/bin/git).
> 
> Git uses threads.  I expect the problem is thread related since it
> doesn't
> happen all the time, and for that reason it might not be reproducible
> running under gdb..

I've put together the used git executable as well as 4 core dumps at 
http://opensource.sf-tec.de/git-crash.tar.bz2

It would be nice if you could take a look and tell me if this gives you 
anything.

Greetings,

Eike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2012-12-31 11:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-27  9:42 Random crashes when calling git Rolf Eike Beer
2012-12-27 17:09 ` John David Anglin
2012-12-31  8:40   ` Rolf Eike Beer
2012-12-31 11:03   ` Rolf Eike Beer [this message]
2012-12-31 19:19     ` John David Anglin
2012-12-31 19:34       ` Rolf Eike Beer
2013-01-08 14:30       ` Rolf Eike Beer
2013-01-08 14:54         ` John David Anglin

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=3563905.2dklDXemHT@donald.sf-tec.de \
    --to=eike-kernel@sf-tec.de \
    --cc=linux-parisc@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.