public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: m.fortini@selcomgroup.com To: gdb-gnats@sources.redhat.com Subject: server/2487: Remote failure reply: E01 on powerpc with pthreads Date: Fri, 01 Aug 2008 11:18:00 -0000 [thread overview] Message-ID: <20080801111509.22045.qmail@sourceware.org> (raw) >Number: 2487 >Category: server >Synopsis: Remote failure reply: E01 on powerpc with pthreads >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: test-bug >Submitter-Id: net >Arrival-Date: Fri Aug 01 11:18:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: m.fortini@selcomgroup.com >Release: 6.8 >Organization: >Environment: >Description: I built gdb 6.8 for mpc5121 using instructions from http://www.crossplatform.ru/?q=node/385 and started gdbserver on a the remote target on a very simple multi threaded app: ================= CUT HERE ==================== #include <stdio.h> #include <stdlib.h> #include <unistd.h> #include <pthread.h> #define NUM_THREADS 5 void *PrintHello(void *threadid) { int c = 0; int tid; tid = (int)threadid; while (++c < 100) { printf("Hello World! It's me, thread #%d!\n", tid); sleep (1); } pthread_exit(NULL); } int main (int argc, char *argv[]) { printf ("Hello world\n"); pthread_t threads[NUM_THREADS]; int rc, t; for(t=0; t<NUM_THREADS; t++){ printf("In main: creating thread %d\n", t); rc = pthread_create(&threads[t], NULL, PrintHello, (void *)t); if (rc){ printf("ERROR; return code from pthread_create() is %d\n", rc); exit(-1); } } pthread_exit(NULL); } ================= CUT HERE ==================== I used the cross gdb on a 686 host, setting the right sysroot, but I cannot set any breakpoints on the remote target. If I continue the program, I get.. Packet received: qSymbol:5f7468726561645f64625f707468726561645f6b65795f646174615f6c6576656c325f64617461 Sending packet: $qSymbol:ffda3bc:5f7468726561645f64625f707468726561645f6b65795f646174615f6c6576656c325f64617461#e9...Ack Packet received: qSymbol:5f7468726561645f64625f6c696e6b5f6d61705f6c5f746c735f6d6f646964 Sending packet: $qSymbol:ffda3c8:5f7468726561645f64625f6c696e6b5f6d61705f6c5f746c735f6d6f646964#6a...Ack Packet received: qSymbol:5f7468726561645f64625f6474765f647476 Sending packet: $qSymbol:ffda3d4:5f7468726561645f64625f6474765f647476#f7...Ack Packet received: qSymbol:5f7468726561645f64625f6474765f745f706f696e7465725f76616c Sending packet: $qSymbol:ffda3e0:5f7468726561645f64625f6474765f745f706f696e7465725f76616c#0c...Ack Packet received: qSymbol:5f7468726561645f64625f707468726561645f64747670 Sending packet: $qSymbol:ffda284:5f7468726561645f64625f707468726561645f64747670#d4...Ack Packet received: qSymbol:5f7468726561645f64625f636f6e73745f7468726561645f61726561 Sending packet: $qSymbol::5f7468726561645f64625f636f6e73745f7468726561645f61726561#47...Ack Packet received: qSymbol:5f7468726561645f64625f72656769737465723634 Sending packet: $qSymbol:ffda3f8:5f7468726561645f64625f72656769737465723634#07...Ack Packet received: qSymbol:5f7468726561645f64625f72656769737465723332 Sending packet: $qSymbol:ffda3ec:5f7468726561645f64625f72656769737465723332#2c...Ack Packet received: qSymbol:5f7468726561645f64625f726567697374657236345f7468726561645f61726561 Sending packet: $qSymbol::5f7468726561645f64625f726567697374657236345f7468726561645f61726561#fb...Ack Packet received: qSymbol:5f7468726561645f64625f726567697374657233325f7468726561645f61726561 Sending packet: $qSymbol::5f7468726561645f64625f726567697374657233325f7468726561645f61726561#f6...Ack Packet received: OK Sending packet: $qSymbol::#5b...Ack Packet received: OK Sending packet: $m4800eb7c,4#fa...Ack Packet received: 9421fff0 Sending packet: $vCont;s:6c7#c2...Ack Packet received: T0501:bfbaf8d0;40:4800eb80;thread:6c7; Sending packet: $m4800eb7c,4#fa...Ack Packet received: 9421fff0 Sending packet: $X4800eb7c,4:}]\202\020\b#93...Ack Packet received: OK Sending packet: $m1000057c,4#8d...Ack Packet received: 38000000 Sending packet: $X1000057c,4:}]\202\020\b#26...Ack Packet received: OK Sending packet: $vCont;c#a8...Ack Packet received: E01 warning: Remote failure reply: E01 >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2008-08-01 11:18 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20080801111509.22045.qmail@sourceware.org \ --to=m.fortini@selcomgroup.com \ --cc=gdb-gnats@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).