public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "pedro at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/10737] catch syscall name mappings (xml) should be per-arch or per-target, not global
Date: Tue, 06 Oct 2009 10:53:00 -0000	[thread overview]
Message-ID: <20091006105334.27640.qmail@sourceware.org> (raw)
In-Reply-To: <20091006104401.10737.pedro@codesourcery.com>


------- Additional Comments From pedro at codesourcery dot com  2009-10-06 10:53 -------
This isn't that a big deal currently, it's more a design issue,
as only the linux native target catching syscalls
as of 7.0.  To reproduce this, I guess one only needs to
start with a --enable-targets=all gdb, and do:

$ gdb ./my_cross_binary_of_some_random_architecture_not_the_native
(gdb) catch syscall 123
<123 will be mapped using the native target's syscall mappings>

I think currently GDB will then error out when the user connects
to the remote end with "target remote", since the remote target
doesn't support target_set_syscall_catchpoint.


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1


http://sourceware.org/bugzilla/show_bug.cgi?id=10737

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  reply	other threads:[~2009-10-06 10:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06 10:44 [Bug gdb/10737] New: " pedro at codesourcery dot com
2009-10-06 10:53 ` pedro at codesourcery dot com [this message]
     [not found] <bug-10737-4717@http.sourceware.org/bugzilla/>
2014-10-08 19:10 ` [Bug gdb/10737] " sergiodj at redhat dot com
2014-10-13  0:23 ` sergiodj at redhat dot com
2014-10-16  4:03 ` sergiodj at redhat dot com
2014-10-17 11:44 ` palves at redhat dot com
2014-11-14  1:43 ` sergiodj at redhat dot com
2014-11-20 17:33 ` cvs-commit at gcc dot gnu.org
2014-11-20 18:35 ` cvs-commit at gcc dot gnu.org
2014-12-25  0: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=20091006105334.27640.qmail@sourceware.org \
    --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).