This bug seems to have been reported several times. I could even reproduce it twice since the last release.
It appears that the treeview sorting code tries to send a message to a random object. This is surely a memory corruption issue. However, I could reproduce the problem with a smaller library, so I do not think the size is important here. This problem will be fixed in the next release. It is weird that you do not get any tracebacks. Could you try to run alexandria like this: $ DEBUG=1 alexandria And paste the result somewhere? Thanks Laurent On Thu, 13 Jan 2005 13:22:25 +0000, Dafydd Harries <[EMAIL PROTECTED]> wrote: > > I'm sending this to the Alexandria mailing list. > > Hi Alexandria people -- this is a bug report filed in the Debian bug > tracking system about a crash in Alexandria. Most of the relevant > information should be included below, but the full report is available > here: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=290180 > > Ar 13/01/2005 am 07:13, ysgrifennodd David Weinehall: > > On Thu, Jan 13, 2005 at 12:58:05AM +0000, Dafydd Harries wrote: > > > Ar 13/01/2005 am 00:25, ysgrifennodd David Weinehall: > > > > When you have a sufficiently sized book collection, Alexandria will > > > > crash if started in, or switched to, list mode. It will also crash if > > > > you try to rearrange the sort order. > > > > > > > > Trial and error shows that 140 titles works, while 141 titles or more > > > > causes the crash; cover pictures or not doesn't matter. > > > > > > Hmm, I would expect this to be something to do with the 141st title in > > > question rather than the number 141. > > > > This seems a tad bit unlikely, since I have tried different permutations > > of books (sorry, I guess I should've mentioned that in the original report). > > I will try to repeat the tests on a machine that only uses the libraries > > from unstable; on my two main systems I have a few libraries from > > experimental installed. > > Ah, ok. Perhaps 141 is a magic number then. :) > > > > Did you see any tracebacks on Alexandria's standard output from these > > > crashes? If there are any, appending them to the bug report would be > > > useful. > > > > No, there were no tracebacks at all. > > Hmm, that's unexpected. > > > Oh, as a further data point; the reason I tagged the bug upstream is > > that I downloaded the upstream source and tested that one too, just to > > make sure the bug was not Debian specific. > > Yes, I agree that it's an upstream bug. > > -- > Dafydd > _______________________________________________ > Alexandria-list mailing list > [EMAIL PROTECTED] > http://rubyforge.org/mailman/listinfo/alexandria-list > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
