[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[cdt-dev] Suggestion for a more efficient stackframe updating
|
When the CDT debugger becomes suspended, it updates the list of threads
and then updates the stackframes and variables for each thread. This can
be very time consuming when debugging a remote embedded target with many
threads. Why must the CDT debugger update the stackframes and variables
for _each_ thread? It would be much more efficient to just update the
stackframes and variables for the _current_ thread. If the user selects
another thread, then the stackframes and variables for that thread would
be updated. UI-wise, this would probably mean that only the current
thread is expanded while all other threads are collapsed. Selecting a
new current thread updates and expands that thread and collapses the
previously current thread.
Of course, this new behaviour could be made as a preferences setting,
where the original behaviour is the default option.
Regards,
Stefan
begin:vcard
fn:Stefan Bylund
n:Bylund;Stefan
org:Enea Embedded Technology AB
adr;quoted-printable;quoted-printable:;;Nytorpsv=C3=A4gen 5B, Box 232;T=C3=A4by;;183 23;Sweden
email;internet:steby@xxxxxxx
title:Software Engineer
tel;work:+46 8 50714000
tel;cell:+46 709 714325
url:http://www.ose.com
version:2.1
end:vcard
