RE: [litwindow-users] Re: vs 2005 compilation

[yrs90 <yr...@ya...>]

> > Any idea how to resolve this assertion?  Is this a library problem too?
> Looks very much like it, I'd say.

I'm thinking that this might not be a library problem.  I've been tracing
through the function and I watch it iterate through the name space looking
for "Items".  

I conjectured that this might be related to something I mishandled in
wxCtrlListAdapter, so I've now tried it with a wxListBox and the same thing
happens.  The following uses wxListBox. (wxListCtrl followed the same path.)

The problem occurs after the symbol is successfully located in
lwListAdapterBase.  It has started to unwind.  The failure occurs as at
rc==currentAggregate.end() at line 465 of dataadapterimp.cpp.  During the
operator== function, the iterator check occurs and, in this case, fails.

The iterator rc was just returned from find_identifier via "return
nested_rc". It is at the wxListBoxAdapter level comparing to the iterator
returned on lwListAdapterBase.

rc.it._Mycont == 0x877804 while the currentAggregate.end().it._Mycont ==
0x877b04.  Since the two values of _Mycont are not equal the assertion
occurs.

The usual course is that it still turns out to be something I've done. :)
Still, any thoughts?


> I have got a question. You are using the free 2003 tools. They come 
> without the debugging libraries you say. But you could still generate 
> debugging information with the compiler, couldn't you? Then I would 
> suggest you continue to use the free tools, add the debug symbols 
> compiler switch and compile and link the whole thing. You don't need to 
> link with the debugging libraries to be able to debug. All you need is 
> debug symbols.

This is a great idea!  The only thing is that I don't know how to extract
the symbols from the obj files without the linkers help.

Regards,
Joel


---
[This E-mail scanned for viruses by Declude Virus]