[wx-dev] Re: enhancements to wxStackFrame for Linux

[Vadim Zeitlin]

On Wed, 01 Nov 2006 15:37:50 +0100 Francesco Montorsi <f18m_cpp217828 at yahoo.it> wrote:

FM> since calling addr2line only once means that in any case we must keep in 
FM> memory the result of all the parsing,

 This is the main thing which I wanted to say in my comment to the bug.
Currently we don't do this and get the location information for each frame
separately, but we should get them all at once and then store them
somewhere. Whether we do it in wxStackWalker or wxStackFrame itself is not
really important, just as you say.

FM> >  So while I do agree with Vaclav's suggestion to use wxCollapsiblePane in
FM> > the generic version (BTW, this reminds me that it would probably make sense
FM> > to use it in wxLog dialog too), I'd like to continue using wxMessageBox
FM> > under Windows.
FM> ok, but under wxGTK I'd say to use this new generic version as default 
FM> since currently reading all the stack frame wrapped by the dialog is a 
FM> pain (I don't remember right now - do the stack trace gets wrapped on 
FM> wxMSW's msgbox ?).

 No, I don't think so. I don't remember them being wrapped to unreadable
state under GTK neither however...

FM> Also, I propose to strip the arguments from the function names 
FM> (fnc(typeA a, typeB b, typeC c) => fnc); e.g. wxOnAssert takes a lot of 
FM> arguments making the line for that call very long. And they are not very 
FM> useful to the developer...

 I disagree, they can be very useful if you have several overloaded
functions.

 Regards,
VZ