From: Tom Tromey <tromey@redhat.com>
To: David Daney <ddaney@caviumnetworks.com>
Cc: gdb-patches@sourceware.org, Nathan Froyd <froydnj@codesourcery.com>
Subject: Re: [Patch v2] Add mips*-linux* catch syscall support.
Date: Fri, 04 Feb 2011 16:11:00 -0000 [thread overview]
Message-ID: <m3hbcjbwzu.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4D3DD73C.9060201@caviumnetworks.com> (David Daney's message of "Mon, 24 Jan 2011 11:47:08 -0800")
>>>>> "David" == David Daney <ddaney@caviumnetworks.com> writes:
Oh, yeah...
David> I think the real fix for this is to improve the core 'catch syscall'
David> support so that it can either remember the syscall number, or not try
David> to print out bogus information, but that would be something for a
David> different patch.
Could you file this in bugzilla?
Tom
prev parent reply other threads:[~2011-02-04 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 20:20 David Daney
2011-01-31 19:00 ` Ping: " David Daney
2011-01-31 19:52 ` Michael Snyder
2011-01-31 20:08 ` David Daney
2011-02-04 16:11 ` Tom Tromey
2011-02-04 16:11 ` Tom Tromey [this message]
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=m3hbcjbwzu.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=ddaney@caviumnetworks.com \
--cc=froydnj@codesourcery.com \
--cc=gdb-patches@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).