| potential GDB debugging in CDT speed improvement? [message #210578] |
Tue, 26 February 2008 14:58 |
Eclipse User |
|
|
|
Originally posted by: clen.sjm.som
I've noticed that while debugging in Eclipse CDT (3.2 with CDT 3.1.x, or
3.3 with CDT 4.x), the GDB call "info sharedlibrary" is made after each
instruction while stepping through code (x86 or ARM Linux target). This
call basically lists what shared libraries relavant to the process are
loaded, and at what addresses.
What I find puzzling is why this information isn't cached , as (to my
understanding), these offsets do not chance for the life of the
process/thread. It seems to be an expensive call (sometimes taking
0.5-0.75 sec to return); perhaps there is room for improvement by caching
this on the CDT side? (It adds a noticeable delay to rendering / updating
Eclipse Debugging UI) Please correct me if I am missing something.
-Chris Len
Linux Software Engineer
St. Jude Medical
|
|
|
Powered by
FUDForum. Page generated in 0.04209 seconds
Home