public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "wenyan.xin at windriver dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27780] New: not report warning when set a breakpoint at invalid address for arm64
Date: Tue, 27 Apr 2021 02:02:09 +0000	[thread overview]
Message-ID: <bug-27780-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=27780

            Bug ID: 27780
           Summary: not report warning when set a breakpoint at invalid
                    address for arm64
           Product: gdb
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: wenyan.xin at windriver dot com
  Target Milestone: ---

we are developing a Gdb Server on VxWorks for arm64.

on gdb client side, I used the following command and got output.

(gdb) b *0
Breakpoint 2 at 0x0
(gdb) c
Continuing.
[Inferior 1 (process 1) exited normally]
(gdb)


Since the 0 address breakpoint is invalid, so the output should be as
following:

(gdb) b *0
Breakpoint 2 at 0x0
(gdb) c
Continuing.
Warning:
Cannot insert breakpoint 2.
Cannot access memory at address 0x0

Command aborted.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2021-04-27  2:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27  2:02 wenyan.xin at windriver dot com [this message]
2021-04-27  2:16 ` [Bug gdb/27780] " wenyan.xin at windriver dot com
2021-04-27  7:28 ` wenyan.xin at windriver dot com
2021-04-27  8:22 ` wenyan.xin at windriver dot com
2021-04-30  5:07 ` wenyan.xin at windriver dot com
2022-11-02 12:03 ` luis.machado at arm dot com

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-27780-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: link
Be 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).