Message327517
There are a few ways we can go with this, depending on how verbose we want to be and how willing we are to make calls to the data. Here are a few pieces of information we could expose:
- Length
- Whether it's a file or anonymous memory
- The entire contents
- The clipped contents
- Whether it's opened or closed
- The access type
So here's an example:
<mmap.mmap object; length=514 access=ACCESS_READ>
And another:
<mmap.mmap object; length=514 content=b'This is my' ... b'file.'>
I don't know whether we're able to include the file name on there, that would be nice. |
|
Date |
User |
Action |
Args |
2018-10-11 04:57:46 | cool-RR | set | recipients:
+ cool-RR, eric.smith, xtreak |
2018-10-11 04:57:46 | cool-RR | set | messageid: <1539233866.17.0.788709270274.issue34953@psf.upfronthosting.co.za> |
2018-10-11 04:57:46 | cool-RR | link | issue34953 messages |
2018-10-11 04:57:45 | cool-RR | create | |
|