All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: Git Mailing List <git@vger.kernel.org>
Subject: qgit segfaults after b237b00
Date: Tue, 12 Sep 2006 12:01:27 +0200	[thread overview]
Message-ID: <45068577.2020608@op5.se> (raw)

What subject says, really. Tried cold cache, hot cache, with and without 
qgit.dat, 3 different repos and 14 different repo-tips. Same result 
every time. A segfault before anything is drawn.

Backtrace isn't very helpful (to me anyways):
#0  0x00000000 in ?? ()
(gdb) bt
#0  0x00000000 in ?? ()
#1  0x458525d2 in QGVector::insert () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#2  0x080aa19a in MainImpl::setupPixmaps (this=0x8191520, h=18)
     at /usr/lib/qt-3.3/include/qptrvector.h:67
#3  0x080b1ad1 in MainImpl::adjustFontSize (this=0x8191520, delta=0)
     at mainimpl.cpp:981
#4  0x080bae05 in MainImpl (this=0x8191520, cd=@0xbf92b094, p=0x0, name=0x0)
     at mainimpl.cpp:142
#5  0x080c4cdf in main (argc=0, argv=0x0) at qgit.cpp:14
(gdb) quit

c++ is a scary thing to me, and my familiarity with QT is akin to the 
common cavemans grasp of piloting fighter-jets. I thus refrain from 
guessing where the problem might be.

qgit-1.5.1 works wonderfully, so I've reset to that and am using it 
meanwhile.

btw, kudos for a great tool.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

             reply	other threads:[~2006-09-12 10:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-12 10:01 Andreas Ericsson [this message]
2006-09-12 17:39 ` qgit segfaults after b237b00 Marco Costalba
2006-09-13  8:45   ` Andreas Ericsson

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=45068577.2020608@op5.se \
    --to=ae@op5.se \
    --cc=git@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.