Jump to content

1 post in this topic

Recommended Posts

Posted

I'm getting closer to getting this thing hacked to pieces. My next hiccup:

 

I need to search the in-use memory ranges for the app. If I debug it in gdb, I can run: info mach-ranges and it shows me every allocated memory range.

 

In lldb... nothing? Nothing I can see anyway... A link I googled said to use image dump sections, but that only shows me the memory ranges of the program itself and it's loaded libraries etc. NOT the memory that the program malloc'ed AFTER it started. 

 

For example, this program malloc's a large 10mb memory range after it fires up. When I run info mach-regions, I can see that range. If I detach, and attach with lldb, and run image dump sections, it doesnt show that range, at all.

 

And no other lldb command I can find will.

 

Any clue how I get this info without using both tools manually? I'm trying to script some stuff. Doing this part manually really kills the whole "script it so its faster" thing.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
  • Create New...

Important Information

We would like to place cookies on your device to help make this website better. The website cannot give you the best user experience without cookies. You can accept or decline our cookies. You may also adjust your cookie settings. Privacy Policy - Guidelines