Re: Assert errors when starting up

On Mon, 9 May 2005 16:12:51 +1000 Mark Livingstone <[email protected]> wrote:

ML> I know I have mentioned these before but that was pre-wxStackWalker so I have
ML> given the uptodate versions below. They always seem to come in pairs as shown
ML> and occur 4-6 times (each) between starting up M on my Mandrake box. The
ML> strange(?) thing is that they do not occur on my Gentoo based laptop. I have
ML> gtk v1.2.10 on both and M/wxWidgets CVS uptodate. The only diff is that
ML> Mandrake kernel is 2.6.8.1-12 and Gentoo is 2.6.11-r6.

 Do you use the same config file? In particular, do you show the "status"
column in both cases?

ML> Another thing I noticed which might have been there forever is that if I go
ML> into say folder properties, the bottom of the panel is far off the botton of
ML> the screen and even if you try to use resize, it cannot be brought back
ML> onscreen. The panel width can be adjusted but not the height. Even clicjking
ML> the fullscreen icon does not bring the bottom onscreen.

 This is definitely a bug, the panel should be shrinkable down to < 600
pixels and I think you screen should be taller than that, right?

ML> Call stack:
ML> [05] wxStackWalker::Walk(unsigned int)       
ML> [06] 0x40614e5d
ML> [07] wxAppConsole::OnAssert(char const*, int, char const*, char const*)
ML> [08] wxApp::OnAssert(char const*, int, char const*, char const*)
ML> [09] wxMApp::OnAssert(char const*, int, char const*, char const*)
ML> [10] wxOnAssert(char const*, int, char const*, char const*)
ML> [11] wxAssert(int, char const*, int, char const*, char const*)
ML> [12] wxListBase::Item(unsigned int) const    
ML> [13] wxListHeaderDataList::Item(unsigned int) const
ML> [14] wxListMainWindow::SetColumn(int, wxListItem&)
ML> [15] wxGenericListCtrl::SetColumn(int, wxListItem&)
ML> [16] wxListView::SetColumnImage(int, int)    
ML> [17] wxFolderListCtrl::UpdateThreadIndicator()

 I've added a check that the status column is shown here, hopefully it
should fix this. If not, please try attach gdb to the program the next time
this happens (run "gdb M" and type "attach <pid>" inside gdb) and please
look at m_columns array values ("p m_columns[0]", "p m_columns[1]", ...).

 Thanks!
VZ



-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click