From: oza Pawandeep <oza.pawandeep@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
gdb@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [design change] record-replay linux ABI level
Date: Tue, 05 Jun 2012 09:19:00 -0000 [thread overview]
Message-ID: <CAK1A=4xEpL5TiTZsBDUaHSe+taYuXDeoeO0D1M=p-6JXty5a_w@mail.gmail.com> (raw)
In-Reply-To: <874nrgrx70.fsf@fleche.redhat.com>
I have gone through some of the xml stuffs already done.
under gdb/syscalls/arch_linux.xml files exist. which is currently not
used for record-purpose.
there are 2 ways we could go ahead now:
1) use the above file for recording purpose too and define new
arm-linux.xml for arm specific syscalls.
2) or we decide to keep only one combined xml files for record-replay
future for all arch.
PS: syscall code is almost done now, it supports 242 syscalls
[till gdb_sys_sched_getaffinity = 242]
(xml stuff is pending, for which either approach 1) or 2) could be taken.)
Regards,
Oza.
On Wed, May 16, 2012 at 8:26 PM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "oza" == oza Pawandeep <oza.pawandeep@gmail.com> writes:
>
> oza> b) I am not much familiar with xml generated C files, and where to
> oza> change in gdb, but with that, will the record_linux_system_call be
> oza> able to incorporate all conflicting syscall numbers in that case ?
>
> The idea is to extend the current approach. That is, have a single
> generic enum; then map the system-specific numbers to this enum. The
> difference is that the mappings would be generated from the XML files.
>
> oza> define as follows
> oza> enum gdb_syscall
> oza> {
> oza> /* i386 related syscalls */
> oza> /* ARM related syscalls */
> oza> /* MIPS related syscalls */
> oza> so on..
> oza> }
>
> Yeah, I don't like this much.
>
> Tom
next prev parent reply other threads:[~2012-06-05 9:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAK1A=4xtgYd8hQEwHxjLQiv4eqhCu0cSRDmmbFJvBDJwDxUM+Q__46748.0269181125$1336555010$gmane$org@mail.gmail.com>
2012-05-09 20:39 ` Tom Tromey
2012-05-10 8:49 ` oza Pawandeep
[not found] ` <CAK1A=4xbh0M=yfc2MQpZdDCJEPnL3_z8=TA0VSE7qVCoO0Dn-Q__42617.423789534$1336639800$gmane$org@mail.gmail.com>
2012-05-10 13:39 ` Tom Tromey
2012-05-13 7:19 ` oza Pawandeep
2012-05-13 7:33 ` oza Pawandeep
2012-05-13 9:47 ` oza Pawandeep
2012-05-14 14:57 ` Joel Brobecker
2012-05-15 5:20 ` oza Pawandeep
2012-05-15 5:34 ` Joel Brobecker
[not found] ` <CAK1A=4yervLeVDQ-r49n95ftrB27u8K+R1hfstz1oFwTNX=t7Q__24807.0006179207$1337059251$gmane$org@mail.gmail.com>
2012-05-15 16:42 ` Tom Tromey
2012-05-16 10:48 ` oza Pawandeep
2012-05-16 14:57 ` Tom Tromey
2012-06-05 9:16 ` oza Pawandeep
2012-06-06 18:17 ` Tom Tromey
2012-06-05 9:19 ` oza Pawandeep [this message]
2012-05-09 9:16 oza Pawandeep
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='CAK1A=4xEpL5TiTZsBDUaHSe+taYuXDeoeO0D1M=p-6JXty5a_w@mail.gmail.com' \
--to=oza.pawandeep@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
--cc=tromey@redhat.com \
/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).