{"thread":{"id":"5542","subject":"qgit segfaults after b237b00","startedAt":"2006-09-12T10:01:27Z","lastAt":"2006-09-13T08:45:30Z","messageCount":3,"participants":["Andreas Ericsson","Marco Costalba"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"26771","messageId":"45068577.2020608@op5.se","threadId":"5542","inReplyTo":null,"subject":"qgit segfaults after b237b00","fromName":"Andreas Ericsson","fromEmail":"ae@op5.se","sentAt":"2006-09-12T10:01:27Z","receivedAt":"2006-09-12T10:01:27Z","isPatch":false,"sender":{"key":"ae@op5.se","avatar":"https://gravatar.com/avatar/426e89595c75a8f5252dd0c989e5fabe5bcac616e68557427ad9aef6b0ca342a?d=mp&s=160"},"body":"What subject says, really. Tried cold cache, hot cache, with and without \nqgit.dat, 3 different repos and 14 different repo-tips. Same result \nevery time. A segfault before anything is drawn.\n\nBacktrace isn't very helpful (to me anyways):\n#0 0x00000000 in ?? ()\n(gdb) bt\n#0 0x00000000 in ?? ()\n#1 0x458525d2 in QGVector::insert () from /usr/lib/qt-3.3/lib/libqt-mt.so.3\n#2 0x080aa19a in MainImpl::setupPixmaps (this=0x8191520, h=18)\n at /usr/lib/qt-3.3/include/qptrvector.h:67\n#3 0x080b1ad1 in MainImpl::adjustFontSize (this=0x8191520, delta=0)\n at mainimpl.cpp:981\n#4 0x080bae05 in MainImpl (this=0x8191520, cd=@0xbf92b094, p=0x0, name=0x0)\n at mainimpl.cpp:142\n#5 0x080c4cdf in main (argc=0, argv=0x0) at qgit.cpp:14\n(gdb) quit\n\nc++ is a scary thing to me, and my familiarity with QT is akin to the \ncommon cavemans grasp of piloting fighter-jets. I thus refrain from \nguessing where the problem might be.\n\nqgit-1.5.1 works wonderfully, so I've reset to that and am using it \nmeanwhile.\n\nbtw, kudos for a great tool.\n\n-- \nAndreas Ericsson andreas.ericsson@op5.se\nOP5 AB www.op5.se\nTel: +46 8-230225 Fax: +46 8-230231\n"},{"id":"26774","messageId":"e5bfff550609121039h1ef25bc8y25186c321d555b8e@mail.gmail.com","threadId":"5542","inReplyTo":"45068577.2020608@op5.se","subject":"Re: qgit segfaults after b237b00","fromName":"Marco Costalba","fromEmail":"mcostalba@gmail.com","sentAt":"2006-09-12T17:39:30Z","receivedAt":"2006-09-12T17:39:30Z","isPatch":false,"sender":{"key":"mcostalba@gmail.com","avatar":null},"body":"Hi Andreas,\n\nOn 9/12/06, Andreas Ericsson wrote:\n> What subject says, really. Tried cold cache, hot cache, with and without\n> qgit.dat, 3 different repos and 14 different repo-tips. Same result\n> every time. A segfault before anything is drawn.\n>\n\nSorry but I am not able to reproduce the bug here. Also from the trace I see\nthat the segfault happens in a part of code that has not been touched\nby b237b00.\nAnd that _should_ not segfault in any way.\n\nThe code there is the same of qgit-1.5.1 so perhaps could be some\nplatform related issue,\nplease write me Qt and gcc versions and processor used and, in case,\ndo a complete rebuild with also reconfiguration (autoreconf -i).\n\nWhat about the current qgit HEAD (6128112f36) , could you reproduce\nthe bug also there?\n\n>From the trace I see the segfault occurs in main view constructor,\ni.e. before to touch anything.\nSo it is not related to a particular repository.\n\n> c++ is a scary thing to me,\n\nC++ is really scary not because we don't understand the code, but\nbecause we _think_ to understand what the code does ;-)\n\nPrinciple of least surprise is not exactly one of the design\ncornerstones of C++, at least for normal people sense of surprise.\n\n>\n> btw, kudos for a great tool.\n>\nThanks to you for using it, and reporting bugs.\n\nAny suggestion is very appreciated!\n\n Marco\n"},{"id":"26793","messageId":"4507C52A.6040902@op5.se","threadId":"5542","inReplyTo":"e5bfff550609121039h1ef25bc8y25186c321d555b8e@mail.gmail.com","subject":"Re: qgit segfaults after b237b00","fromName":"Andreas Ericsson","fromEmail":"ae@op5.se","sentAt":"2006-09-13T08:45:30Z","receivedAt":"2006-09-13T08:45:30Z","isPatch":false,"sender":{"key":"ae@op5.se","avatar":"https://gravatar.com/avatar/426e89595c75a8f5252dd0c989e5fabe5bcac616e68557427ad9aef6b0ca342a?d=mp&s=160"},"body":"Marco Costalba wrote:\n> Hi Andreas,\n> \n> On 9/12/06, Andreas Ericsson wrote:\n>> What subject says, really. Tried cold cache, hot cache, with and without\n>> qgit.dat, 3 different repos and 14 different repo-tips. Same result\n>> every time. A segfault before anything is drawn.\n>>\n> \n> Sorry but I am not able to reproduce the bug here. Also from the trace I \n> see\n> that the segfault happens in a part of code that has not been touched\n> by b237b00.\n> And that _should_ not segfault in any way.\n> \n> The code there is the same of qgit-1.5.1 so perhaps could be some\n> platform related issue,\n\nProbably, yes. Some more digging indicates it comes from trying to fetch \nthe system default-font and setting it as the default application-font.\n\n> please write me Qt and gcc versions and processor used and, in case,\n> do a complete rebuild with also reconfiguration (autoreconf -i).\n> \n\nNaturally. Forgot it in the first mail *blush*. Mainly running Fedora \nCore 5, except for the kernel which I compile myself.\n\nnox!exon:~/git/qgit$ gcc --version\ngcc (GCC) 4.1.1 20060525 (Red Hat 4.1.1-1)\nCopyright (C) 2006 Free Software Foundation, Inc.\nThis is free software; see the source for copying conditions. There is NO\nwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.\n\nnox!exon:~/git/qgit$ rpm -q qt\nqt-3.3.6-0.4.fc5\nnox!exon:~/git/qgit$ uname -a\nLinux nox.op5.se 2.6.18-rc6 #1 Wed Sep 6 15:41:35 CEST 2006 i686 i686 \ni386 GNU/Linux\nnox!exon:~/git/qgit$\n\n\nRebuilding with full autoreconf -i does indeed seem to solve the \nproblem. I'm guessing some yum update changed the qt-version and the \nconfigure.cache kept the old settings so that it wasn't checked.\n\nSorry for the noise.\n\n-- \nAndreas Ericsson andreas.ericsson@op5.se\nOP5 AB www.op5.se\nTel: +46 8-230225 Fax: +46 8-230231\n"}]}