public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "qiyao at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug server/18130] New: gdbserver event loop is terminated by exception
Date: Mon, 16 Mar 2015 09:17:00 -0000	[thread overview]
Message-ID: <bug-18130-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 18130
           Summary: gdbserver event loop is terminated by exception
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: server
          Assignee: unassigned at sourceware dot org
          Reporter: qiyao at gcc dot gnu.org

On arm-linux, when I set hardware watchpoint on some address which doesn't meet
the kernel alignment requirement, like this,

(gdb) ./gdb -ex "target remote arm-linux:2346" -ex "b main" -ex "c" -ex "watch
*(buf.byte + 1 + 1)@1" -ex "stepi" -ex "quit"
gdb/testsuite/gdb.base/watchpoint-reuse-slot

the gdbserver is terminated like this:

Killing process(es): 9846
input_interrupt, count = 1 c = 36 ('$')
Can't determine port: Bad file descriptor.
Exiting

in gdbserver/linux-arm-low.c:arm_prepare_to_resume, hardware debugging
registers are updated by ptrace (PTRACE_SETHBPREGS), and if something is wrong,
exception is thrown out by perror_with_name.

      if (ptrace (PTRACE_SETHBPREGS, pid,
              (PTRACE_TYPE_ARG3) -((i << 1) + 2),
              &proc_info->wpts[i].control) < 0)
        perror_with_name ("Unexpected error setting watchpoint");
      }

The exception isn't caught and event loop is terminated as a result.

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


             reply	other threads:[~2015-03-16  9:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16  9:17 qiyao at gcc dot gnu.org [this message]
2015-03-16  9:32 ` [Bug server/18130] " qiyao 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-18130-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).