search

0vercl0k / lockmem

This utility allows you to lock every available memory regions of an arbitrary process into its working set.
MIT License
64 stars 14 forks source link

Source Code Updates? #5

Closed kiwids0220 closed 10 months ago

kiwids0220 commented 10 months ago

Greetings! I was trying to re-use the code to lock a process' memory in my harness. But after porting the code. I ran into issues like shown below:

image

And If I run the released .exe, which works just fine xD. So not sure if this is the most up-to-date source... image

Thank you!

0vercl0k commented 10 months ago

Let me take a look at this in December - I am currently on vacation, sorry!

Cheers

On Fri, Nov 10, 2023 at 7:48 PM kiwids @.***> wrote:

Greetings! I was trying to re-use the code to lock a process' memory in my harness. But after porting the code. I ran into issues like shown below:

[image: image] https://user-images.githubusercontent.com/60630639/282153484-68234fb3-7faa-4412-a1f0-c1a912159292.png

And If I run the released .exe, which works just fine xD. So not sure if this is the most up-to-date source... [image: image] https://user-images.githubusercontent.com/60630639/282153761-21fc6358-dcba-4cea-b181-9daaa596a9e9.png

Thank you!

— Reply to this email directly, view it on GitHub https://github.com/0vercl0k/lockmem/issues/5, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALIORN5NCLD3NDJROYCYLDYDZZIHAVCNFSM6AAAAAA7GSI2OGVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE4DQMJYGMYTAOA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

kiwids0220 commented 10 months ago

Please take the time off for as long as you need, no rush here! Thanks alot!

Let me take a look at this in December - I am currently on vacation, sorry!

Cheers

On Fri, Nov 10, 2023 at 7:48 PM kiwids @.***> wrote:

Greetings! I was trying to re-use the code to lock a process' memory in my

harness. But after porting the code. I ran into issues like shown below:

[image: image]

https://user-images.githubusercontent.com/60630639/282153484-68234fb3-7faa-4412-a1f0-c1a912159292.png

And If I run the released .exe, which works just fine xD. So not sure if

this is the most up-to-date source...

[image: image]

https://user-images.githubusercontent.com/60630639/282153761-21fc6358-dcba-4cea-b181-9daaa596a9e9.png

Thank you!

—

Reply to this email directly, view it on GitHub

https://github.com/0vercl0k/lockmem/issues/5, or unsubscribe

https://github.com/notifications/unsubscribe-auth/AALIORN5NCLD3NDJROYCYLDYDZZIHAVCNFSM6AAAAAA7GSI2OGVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE4DQMJYGMYTAOA

.

You are receiving this because you are subscribed to this thread.Message

ID: @.***>

0vercl0k commented 10 months ago

I just took a look at this - it seems that maybe you are not reading the latest version of the source code?

Those printf calls are commented: https://github.com/0vercl0k/lockmem/blob/v0.2/src/lockmem.cc#L133

Or I misunderstood the question :)

Cheers

0vercl0k commented 10 months ago

Feel free to re-open if I misunderstood :)

Cheers