[cdt-debug-dev] [cdt-patch] Proposed CDT 1.2 patches 1/3 (fwd)

["Alain Magloire" <alain@xxxxxxx>]

> From: Ashish Karkare <ashish.karkare@xxxxxxxxxxx>
> 
> 
> CDT 1-2 patch: 1/3
> 
> 1. If the stack-info-depth command on one of the threads returns an error,
>     CDT does not display the stack trace for that thread.  This behavior is
>     different from command line gdb, where gdb displays all the frames that it
>     can, and then prints an error message.
> 
>     The proposed patch is to retry the stack-info-depth command- which
>     generally succeeds because gdb patches the offending stack frame- and then
>     display the results.
> 


I see this kind of behaviour on solaris, stack-info-depth fails when debugging a threaded program,
particularly when the thread is not map to a LWP.  In this case, the exception is thrown
and the CDT/Debug/UI just print the thread with a message that the backtrace is not available.

  threa-1 <stackframe not available>

or something similar.

How often that issuing a second command will succeed when the first one fails ?
Did you make a PR for this ?