public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com> To: nobody@sources.redhat.com Cc: gdb-prs@sources.redhat.com, Subject: Re: mi/671: Changing GDB/MI spec say the should be a termination "(gdb)\n" string Date: Fri, 11 Apr 2003 15:38:00 -0000 [thread overview] Message-ID: <20030411153801.18323.qmail@sources.redhat.com> (raw) The following reply was made to PR mi/671; it has been noted by GNATS. From: Andrew Cagney <ac131313@redhat.com> To: gdb-gnats@sources.redhat.com Cc: Subject: Re: mi/671: Changing GDB/MI spec say the should be a termination "(gdb)\n" string Date: Fri, 11 Apr 2003 11:36:51 -0400 > 1:int main() { > 2: int x; > 3: pthread_create(NULL, NULL, routine, NULL); > 4: printf("Hello world\n"); > 5: sleep(200000); // Or a very time consuming function called. > 6: printf("After the long wait\n"); > 7: return 0; > 8:} > > gdb/mi will issue things like: > (gdb) > -break-insert file.c:6 > ^done,bkpt={...} There should be a: (gdb) termination here. > ~"[New Thread 1024 (LWP 30497)]\n" > ~"[Switching to Thread 1024 (LWP 30497)]\n" And here. > .... wait for the sleep .... > *stopped,reason=... > (gdb) > The target being used probably isn't async. Have you tried it with `target remote-async'? Andrew > You do not have the "(gdb)" comming right away. > > OUTPUT ==> (OUT-OF-BAND-RECORD)* [RESULT-RECORD] "(gdb)"nl > > I read the definition like you can accumulate outputs and deal with them only > when encounter "(gdb)" which is true unless you want to wait for the sleep() to > finish. In practice we can consider Out-of-band completely async and should be > process right away. It was not clear at first sight, IMHO.
next reply other threads:[~2003-04-11 15:38 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-11 15:38 Andrew Cagney [this message] 2008-04-20 15:31 drow
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=20030411153801.18323.qmail@sources.redhat.com \ --to=ac131313@redhat.com \ --cc=gdb-prs@sources.redhat.com \ --cc=nobody@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).