This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [design change] record-replay linux ABI level
- From: oza Pawandeep <oza dot pawandeep at gmail dot com>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: Joel Brobecker <brobecker at adacore dot com>, gdb at sourceware dot org, gdb-patches at sourceware dot org
- Date: Tue, 5 Jun 2012 14:49:27 +0530
- Subject: Re: [design change] record-replay linux ABI level
- References: <CAK1A=4xtgYd8hQEwHxjLQiv4eqhCu0cSRDmmbFJvBDJwDxUM+Q__46748.0269181125$1336555010$gmane$org@mail.gmail.com> <87sjf9qecr.fsf@fleche.redhat.com> <CAK1A=4xbh0M=yfc2MQpZdDCJEPnL3_z8=TA0VSE7qVCoO0Dn-Q__42617.423789534$1336639800$gmane$org@mail.gmail.com> <87aa1gqhnq.fsf@fleche.redhat.com> <CAK1A=4wzBfbc1OpbP2BNMGVw0iiWMG81fy1+peq_r5rFkenyhA@mail.gmail.com> <CAK1A=4zRULTC9Tue8Wu7vYpCiHE-sWBLHU7P9uw0d8MO0YRUpA@mail.gmail.com> <CAK1A=4y7d8ot_G+O8oFm_ZVDT9q7QdFu87hMXT=+mHfVuJPnTw@mail.gmail.com> <20120514145650.GF10253@adacore.com> <CAK1A=4yervLeVDQ-r49n95ftrB27u8K+R1hfstz1oFwTNX=t7Q__24807.0006179207$1337059251$gmane$org@mail.gmail.com> <87havhtmzy.fsf@fleche.redhat.com> <CAK1A=4zR6v1-3Mvk9=FS4nAyMHn=UVpj_YDgL=dkHVJz7s1tXQ@mail.gmail.com> <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