From: Joel Brobecker <brobecker@adacore.com>
To: oza Pawandeep <oza.pawandeep@gmail.com>
Cc: Tom Tromey <tromey@redhat.com>,
gdb@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [design change] record-replay linux ABI level
Date: Tue, 15 May 2012 05:34:00 -0000 [thread overview]
Message-ID: <20120515053409.GO10253@adacore.com> (raw)
In-Reply-To: <CAK1A=4yervLeVDQ-r49n95ftrB27u8K+R1hfstz1oFwTNX=t7Q@mail.gmail.com>
> so each arch file would have their own map, compare to current generic
> map in linux-record.h
If I understand what you are saying correctly, I think that this is
what I had in mind.
NB: I should point out that I have little knowledge of the process-
record code. Just trying to help out with possible solutions if
we think the best option is to have one generic enum.
--
Joel
next prev parent reply other threads:[~2012-05-15 5:34 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 [this message]
[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
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=20120515053409.GO10253@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
--cc=oza.pawandeep@gmail.com \
--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).