Kumba wrote: [snip] > Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align > REGINFO 0x1563c0 0x881573c0 0x881573c0 0x00018 0x00018 R 0x4 > LOAD 0x001000 0x88002000 0x88002000 0x13ffc0 0x13ffc0 R E 0x1000 > LOAD 0x141000 0x88142000 0x88142000 0x2b000 0x52400 RWE 0x1000 [snip] > Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align > REGINFO 0x1573c0 0x881573c0 0x881573c0 0x00018 0x00018 R 0x4 > LOAD 0x000000 0x88000000 0x88000000 0x16d000 0x194400 RWE 0x10000 > PAX_FLAGS 0x000000 0x00000000 0x00000000 0x00000 0x00000 0x4 It looks like that pax patch makes the difference. Speculation: With this large alignment, the load would overwrite the exception handlers at 0x80000000 if the firmware wouldn't recognize this area as already in use. Reducing the alignment to 4k may improve things. Btw, an empty segment with no section assigned looks like a bug to me. Btw2, converting the non-writable segment into a writeable one doesn't look like an improvement (but doesn't matter much). Thiemo
