| Remote debug multithread timeout GUI freeze [message #207721] |
Thu, 10 January 2008 07:05  |
Eclipse User |
|
|
|
Originally posted by: raymond.minder.contractors.roche.com
Hello
I am evaluation eclipse with cdt:
My configuration:
Kubuntu Edgy Splash
Eclipse SDK Version: 3.3.1.1
Sun Java 6 Runtime
Target Realtime linux on ARM
Debugger: arm_v4le-gdb GNU gdb 6.3.50.20050810
CDT 4.0.0
I have the following problem by debugging the following program:
#include <pthread.h>
void *print_thread_char(void *ch) {
int i;
for (i=0; i<10000; i++) {
printf("%c\n", *(char*)ch);
}
return NULL;
}
//! Entry point of the tests.
int main(int argc, char *argv[]) {
pthread_t t1, t2;
char ch1='1';
char ch2='2';
pthread_create(&t1, NULL, print_thread_char, &ch1);
pthread_create(&t2, NULL, print_thread_char, &ch2);
pthread_join(t1, NULL);
pthread_join(t2, NULL);
printf("finished \n");
return 0;
}
If I debug the program on the normal PC, the debugging is working.
Even if I set a breakpoint in the function print_thread_char. Everything
is as it should be.
If I remote debug the program on the arm target, it works also okay, as
long as, I do not set a breakpoint in the function print_thread_char. If I
would like to stop the debugger in this function, eclipse freezes and
afterwards the debugging view has the following message behind the tread:
"Thread [2] (Suspended: Breakpoint hit.) <Stack is not available: Target
is not responding (timed out).>"
I also tried to increase the connection timeout to 30000ms.
Then I tried to debug the application via command line. This works fine,
with the same debugger and binary file.
Then I also tried it with the ddd client and everything works fine too.
I use a nfs share to access the binary on the target.
Could somebody help me? Is it a problem in the new cdt?
Thanks a lot
ray
|
|
|
|
Powered by
FUDForum. Page generated in 0.06115 seconds
Home