DynamoRIO Users

Hello all, I am running a client on Windows. The client subscribes to the module load event and for

Another key point is that memtrace_x86.c is using drreg (https://dynamorio.org/page_drreg.html) to

General interval analysis over time has direct support in our analyzer infrastructure: https://

> So it's a bit more difficult to investigate. Also wanted to note the drstatecmp extension (

Describe the bug drmemory on Win10/i686 crashes in dynamorio code To Reproduce Steps to reproduce the

> This is why we generally do not recommend using two clients and instead suggest turning one into

We don't have a tool to convert a trace to an executable binary. We'd appreciate your help to

We have packaged and published a new version 11.0.0 at https://github.com/DynamoRIO/dynamorio/

This is something that is not fully supported today by the front end: https://github.com/DynamoRIO/

Please see https://dynamorio.org/page_debugging.html which says that the first step should always be

I have the exact same issue, except on windows. I've posted in a new conversation my issue with

Thanks for the reply. However, when I run an empty client I still get two times of the running time.

Hi Derek, Thanks for the detailed explanation and the link to the issue! I will try to investigate

As already mentioned, I think you will find that most sources of non-determinism are not from the

My suggestions are mostly general debugging steps that should be applied to any problem. See https://

One issue is that such parent-child relationships are not cross-platform: eg, Windows has no formal

I see, thank you for the "possible leaks" explanation. Could you also explain the jump from

Thank you On Tue, Aug 27, 2024 at 11:16 PM 'Kai Luk' via DynamoRIO Users <dynamorio-users@

Thank you for your suggestion. I tried the command you gave and it worked. :) On Tue, Aug 27, 2024 at

thx again, works like a charm. Peter schrieb am Sonntag, 25. August 2024 um 21:16:24 UTC+2: I did

Hello, I am sorry that I didn't provide my system details. And you are correct. My Host OS:

DR that is statically linked into the application cannot follow across an execve as it has no

It seems like I just didn't actually rebuild the release build with the fix lol. The test passes

Thanks, it is helpful! On Thursday, August 15, 2024 at 11:35:43 PM UTC+8 ky...@google.com wrote:

Sorry for the late replying, I will see and try it, thanks! On Tuesday, August 6, 2024 at 1:32:55 AM

If you're calling compiled code you'll need to save the full state (if you did a clean call

> dr_nonheap_alloc() which allocates cache-reachable space Thanks. I was thinking of something

Got it working! I will clean up the code and upload it to GitHub. On Tuesday, July 23, 2024 at 7:35:

That is the proposal in https://github.com/DynamoRIO/dynamorio/issues/5699 but you can see there a

Hi José, Can you try to use the git repo instead of release tarball? RISC-V support is still