Martin Sevior wrote: > I missed your original post. Can you please tell me how to > reproduce this bug or point me to it's bugzilla entry? I'm a personal > mission to squash all lists related bugs.
Sorry, guess I didn't stick this one in bugzilla (except sort of incidentally -- I mentioned it in 2037 but I don't that will help you). My original post on this bug was http://www.abisource.com/mailinglists/abiword-dev/01/September/0701.html. I thought maybe Mike had found it and fixed it, but I guess his replies don't definitely say that. I haven't seen this problem since them, but I haven't downloaded any newer versions of AbiWord and haven't done much testing since then. Hope this helps, Randy Kramer > > On Thu, 27 Sep 2001, Randy Kramer wrote: > > > Mike Nordell wrote: > > > Randy Kramer wrote: > > > > From the debugger: > > > > > > > > 00479E48 mov ecx,dword ptr [eax+28h] > > > > > > Id say it's fl_BlockLayout::getListAttributesVector, line 5324 in > > > fl_BlockLayout.cpp that SEGV: > > > > > > level = getAutoNum()->getLevel(); > > > > > > getAutoNum() (inlined accessor in fl_Layout.h) returns NULL (or possibly > > > another illegal address, you didn't specify what address the pgm tried to > > > access). > > > > Mike (and everybody), > > > > Oops, sorry -- next time. > > > > Just to clarify things for myself, I'm assuming that anywhere there is > > an instruction like "ecx,dword ptr [eax+28h]" there is a crash waiting > > to happen? > > > > Is there a way to search the entire AbiWord codebase with some regular > > expression to find all the instances of the C++ code that causes the > > problem? (I'm guessing there are some others.) > > > > Just to be clear, I won't be attempting to fix this (I don't think I am > > capable at this point in time -- maybe someday. ;-) > > > > Randy Kramer > > > >
