From: Hui Zhu <teawater@gmail.com>
To: Jiang Jilin <freephp@gmail.com>
Cc: burlen <burlen.loring@gmail.com>,
gdb@sourceware.org, Michael Snyder <msnyder@vmware.com>
Subject: Re: reverse execution
Date: Sun, 18 Oct 2009 03:18:00 -0000 [thread overview]
Message-ID: <daef60380910171945n1354b6bmb0ddf2a3dce80e59@mail.gmail.com> (raw)
In-Reply-To: <7d77a27d0910171802uc09fd78s79c7e9a00fda258b@mail.gmail.com>
Thanks Jilin,
Sorry I made a mistake when we told about it. I want to say 0xf10
series insn (they seems called sse insn), but I said mmx insn.
These 0xf10 insn seems control the xmm reg, you can see the values of
these reg whith gdb cmd "info info all-registers".
Hui
On Sun, Oct 18, 2009 at 09:02, Jiang Jilin <freephp@gmail.com> wrote:
> On Sat, Oct 17, 2009 at 4:34 AM, burlen <burlen.loring@gmail.com> wrote:
>> Is it possible to use reverse execution features on x86-64 linux platform? I
>> turned it on bad things happened. namely sigtrap then sigabrt. it spit out
>> these messages:
>>
>> Process record doesn't support instruction 0xf10 at address 0x7fffdda0dc77.
>> Process record: failed to record execution log.
>
> I checked the opcode 0x0f10, it seems that it hasn't been supported so far,
> either on x86-32 or x86-64. I'm working on it.
>
> Thank you for reporting!
>
>
> To Hui and Michael :
>
> Sorry, I'm a bit busy for looking for jobs these days, so I've to
> delay the work for
> MMX support . And now, I think I should add opcode 0x0f10 support and other
> 2-byte opcodes at first, because they seems more easier to implement.
> Any questions
> please tell me :)
>
> Thanks!
>
> Jiang
>
>> My session follows. Does this mean reverse execution isn't going to work on
>> this platform? or perhaps I have done something wrong in my attempt to use
>> the feature?
>>
>> Thanks
>> Burlen
>>
>>
>> (gdb) run
>> Starting program: /home/burlen/ext/ParaView/PV3-3.7/bin/pvserver
>> [Thread debugging using libthread_db enabled]
>> Listen on port: 11111
>> Waiting for client...
>> Waiting for server...
>> Client connected.
>> ^C
>> Program received signal SIGINT, Interrupt.
>> 0x00007fffe31a66f3 in select () from /lib/libc.so.6
>> (gdb) br vtkOOCFieldTracer::OOCIntegrateOne
>> Breakpoint 1 at 0x7fffdda0b591: file
>> /home/burlen/ext/ParaView/SciVisToolKit/vtkOOCFieldTracer.cxx, line 447.
>> (gdb) cont
>> Continuing.
>>
>> Breakpoint 1, vtkOOCFieldTracer::OOCIntegrateOne (this=0xa77570,
>> oocR=0x1fbff10, fieldName=0xed88b8 "vi", line=0x1fd2020,
>> tcon=0x7fffffffc480) at
>> /home/burlen/ext/ParaView/SciVisToolKit/vtkOOCFieldTracer.cxx:447
>> 447 int w=0;
>> (gdb) target record
>> (gdb) disable 1
>> (gdb) cont
>> Continuing.
>> Process record doesn't support instruction 0xf10 at address 0x7fffdda0dc77.
>> Process record: failed to record execution log.
>>
>> Program received signal SIGTRAP, Trace/breakpoint trap.
>> 0x00007fffdda0dc76 in FieldLine::GetSeedPoint (this=0x1fd2020,
>> p=0x7fffffffc2e0) at /home/burlen/ext/ParaView/SciVisToolKit/FieldLine.h:113
>> 113 p[0]=this->Seed[0];
>> (gdb) cont
>> Continuing.
>> Process record doesn't support instruction 0xf10 at address 0x7fffdda0dc77.
>> Process record: failed to record execution log.
>>
>> Program received signal SIGABRT, Aborted.
>> 0x00007fffdda0dc76 in FieldLine::GetSeedPoint (this=0x1fd2020,
>> p=0x7fffffffc2e0) at /home/burlen/ext/ParaView/SciVisToolKit/FieldLine.h:113
>> 113 p[0]=this->Seed[0];
>> (gdb)
>>
>>
>>
>
>
>
> --
> Jiang
>
next prev parent reply other threads:[~2009-10-18 2:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 21:07 burlen
2009-10-16 21:55 ` Michael Snyder
2009-10-17 23:49 ` Daniel Jacobowitz
2009-10-18 2:19 ` Jiang Jilin
2009-10-18 3:18 ` Hui Zhu [this message]
2009-10-18 4:01 ` Jiang Jilin
2009-10-18 11:18 ` Michael Snyder
2009-10-19 8:04 ` Hui Zhu
2013-04-08 14:37 ishare
2013-04-08 14:47 ` Jan Kratochvil
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=daef60380910171945n1354b6bmb0ddf2a3dce80e59@mail.gmail.com \
--to=teawater@gmail.com \
--cc=burlen.loring@gmail.com \
--cc=freephp@gmail.com \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.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