public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/17471] New: repeating a background command makes it foreground Date: Thu, 09 Oct 2014 13:31:00 -0000 [thread overview] Message-ID: <bug-17471-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=17471 Bug ID: 17471 Summary: repeating a background command makes it foreground Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: palves at redhat dot com Running a background command, and then pressing "enter" to repeat it repeats the same command, but in the foreground. This only happens if the command is passed some extra argument other than the "&", such as "c 1&", "next 2&", "c -a&", etc. Example: (gdb) b foo Breakpoint 2 at 0x4005d4: file bg-execution-repeat.c, line 23. (gdb) c 1& Not stopped at any breakpoint; argument ignored. Continuing. (gdb) Breakpoint 2, foo () at bg-execution-repeat.c:23 23 return 0; /* set break here */ <enter is pressed here> Will stop next time breakpoint 2 is reached. Continuing. *commands here are ignored here, the inferior running in the foreground* ^C Program received signal SIGINT, Interrupt. 0x0000003b36abc6d0 in __nanosleep_nocancel () at ../sysdeps/unix/syscall-template.S:81 81 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) (gdb) -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-10-09 13:31 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-09 13:31 palves at redhat dot com [this message] 2014-10-17 13:30 ` [Bug gdb/17471] " palves at redhat dot com 2014-10-17 13:31 ` palves at redhat dot com 2014-10-29 19:48 ` cvs-commit at gcc dot gnu.org 2014-12-25 0:46 ` cvs-commit at gcc dot gnu.org 2015-08-04 11:44 ` cvs-commit at gcc dot gnu.org 2015-08-25 15:46 ` cvs-commit at gcc dot gnu.org
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=bug-17471-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /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).