public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tui/28483] New: [gdb/tui] breakpoint creation not displayed Date: Thu, 21 Oct 2021 11:20:02 +0000 [thread overview] Message-ID: <bug-28483-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28483 Bug ID: 28483 Summary: [gdb/tui] breakpoint creation not displayed Product: gdb Version: 11.1 Status: NEW Severity: normal Priority: P2 Component: tui Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- Test-case setup: ... $ cat -n hello.c 1 #include <stdio.h> 2 #include <stdlib.h> 3 4 int 5 main (void) 6 { 7 void *p = malloc (10); 8 printf ("hello: %p\n", p); 9 return 0; 10 } $ gcc -g hello.c ... This command: ... $ gdb -q a.out -ex start -ex "tui enable" -ex "b 8" ... gets us in the tui window: ... 2 #include <stdlib.h> 3 4 int 5 main (void) 6 { > 7 void *p = malloc (10); 8 printf ("hello: %p\n", p); 9 return 0; 10 } ... Using system gdb based on 10.1, we have instead: ... 2 #include <stdlib.h> 3 4 int 5 main (void) 6 { > 7 void *p = malloc (10); b+ 8 printf ("hello: %p\n", p); 9 return 0; 10 } ... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-10-21 11:20 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-21 11:20 vries at gcc dot gnu.org [this message] 2021-10-21 11:20 ` [Bug tui/28483] " vries at gcc dot gnu.org 2021-10-21 11:30 ` vries at gcc dot gnu.org 2021-10-21 22:28 ` cvs-commit at gcc dot gnu.org 2021-10-21 22:29 ` vries 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-28483-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).