[Kde-games-devel] Error in KMines game

[Eugene Trounev]

Hi Dimsuz,

Yes, I update every day. So it's still there. Though it doesn't accrue too 
often. In fact I have no idea what one should do to make it fire. But it 
happened to me at least twice esterday.

Best regards,

Eugene
[it-s]

On Friday 27 July 2007 04:16, Dmitry Suzdalev wrote:
> Hi, Eugene!
> First one is a known KHIghscore bug, yes.
>
> The second one is definetly a KMines one, but looks strange - I think
> I have fixed this some time ago.
> Are you sure you can reproduce it with latest sources from svn? :-)
>
> Dmitry.
>
> 2007/7/27, Eugene Trounev <eugene.trounev at gmail.com>:
> > Since we are at it : there seem to be another problem with Kmines (yeah
> > I'm still playing :D )
> >
> > Sometimes if I click beyond the game field (like on the background, or on
> > the
> > field border) game crashes. This is the error it gives in the console:
> > --------------------------------<code-------------------------
> > ASSERT failure in QVector<T>::at: "index out of range",
> > file /usr/include/QtCore/qvector.h, line 284
> > ------------------------------------/>--------------------------
> >
> > Regards,
> >
> > Eugene
> > [it-s]
> >
> > On Thursday 26 July 2007 19:25, Mauricio Piacentini wrote:
> > > Matt Williams wrote:
> > > >> -------------------<code-------------------
> > > >> libkdegames (Highscores): The current high score group "Medium"
> > > >> isn't
> >
> > in
> >
> > > >> the list, adding it
> > > >> ASSERT failure in QList<T>::at: "index out of range",
> > > >> file /usr/include/QtCore/qlist.h, line 371
> > > >> ------------------/>-------------------------
> > > >>
> > > >> Could anyone please take a look at this qlist.h to see what's wrong
> >
> > with
> >
> > > >> it? The error itself does not come up too often thought. Out of 20
> >
> > games
> >
> > > >> maybe once, or twice.
> > > >>
> > > >> Thanks,
> > > >>
> > > >> Eugene
> > > >> [it-s]
> > > >
> > > > That's a bug in KScoreDialog or KHighscore. I'll look into it.
> > >
> > > It might be a bug in KScoreDialog or not: it depends if the highscores
> > > message is being displayed immediately after the crash, is it?
> > > Eugene: if you want to track it down, you can launch the game under
> > > gdb, the debugger. Type
> > >
> > > gdb kmines
> > >
> > > And when it loads, type:
> > >
> > > run
> > >
> > > KMines will then execute inside the debugger. Instead of crashing, it
> > > will stop when the crash happens. You will see additional info in the
> > > console. Type:
> > >
> > > backtrace
> > >
> > > And you will get a list of the calling stack. This is useful to help
> > > developers identify quickly exactly which method caused the error.
> > >
> > > I have not seen this particular issue yet, btw, but I will try to
> > > reproduce it.
> > >
> > > Regards,
> > > Mauricio Piacentini
> > > _______________________________________________
> > > kde-games-devel mailing list
> > > kde-games-devel at kde.org
> > > https://mail.kde.org/mailman/listinfo/kde-games-devel
> >
> > _______________________________________________
> > kde-games-devel mailing list
> > kde-games-devel at kde.org
> > https://mail.kde.org/mailman/listinfo/kde-games-devel
>
> _______________________________________________
> kde-games-devel mailing list
> kde-games-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kde-games-devel