|
m64 format documentation
|
08-22-2019, 05:00 PM
There's nothing interesting in the entire almost-64 kB after the sequence data? Really? Have you checked whether the address value is sign-extended, so an address of e.g. FFFF accesses memory before the sequence? If the memory allocation works similarly to malloc, writing to somewhere around FFF8 or FFFC could corrupt the heap after the sequence is freed.
Sauraen#0047 / SEQ64 developer: https://github.com/sauraen/seq64
|
| Messages In This Thread |
|
m64 format documentation - by simonlindholm - 07-16-2019, 02:33 PM
RE: m64 format documentation - by lezg_g - 08-10-2019, 02:58 AM
RE: m64 format documentation - by Sauraen - 08-16-2019, 05:57 PM
RE: m64 format documentation - by nutta - 08-17-2019, 01:00 PM
RE: m64 format documentation - by simonlindholm - 08-18-2019, 07:03 PM
RE: m64 format documentation - by Sauraen - 08-18-2019, 07:29 PM
RE: m64 format documentation - by simonlindholm - 08-18-2019, 08:42 PM
RE: m64 format documentation - by Sauraen - 08-22-2019, 02:36 AM
RE: m64 format documentation - by simonlindholm - 08-22-2019, 01:06 PM
RE: m64 format documentation - by Sauraen - 08-22-2019, 05:00 PM
RE: m64 format documentation - by simonlindholm - 08-24-2019, 10:37 PM
RE: m64 format documentation - by Sauraen - 08-25-2019, 04:56 PM
|
Wiki
Discord
