On Tue, 2019-06-18 at 13:50 +0200, Mark Wielaard wrote:
> Using ELF_C_WRITE_MMAP sometimes causes unexpected errors when disk
> space is low. When writing out the file, the output file is first
> extended so that it covers the whole file/mmap size. But it might
> be that the file system allowed the
Hi all,
If I have a Elf64_Phdr, why can't I straight change its elements, like, I'm
getting seg fault when trying to do:
(see gdb output)
... received signal SIGSEGV, Segmentation fault.
...
957 oldPhdr->p_vaddr = 0x1235;
(gdb) p/x oldPhdr
$11 = 0x3ffb4bf0040
(gdb) p/x *oldPhdr
$12 = {p_
Hi -
> If I have a Elf64_Phdr, why can't I straight change its elements, like, I'm
> getting seg fault when trying to do:
> (see gdb output)
>
> ... received signal SIGSEGV, Segmentation fault.
> ...
> 957 oldPhdr->p_vaddr = 0x1235;
> (gdb) p/x oldPhdr
> $11 = 0x3ffb4bf0040
The elf_begin(
Hi,
On Wed, 2019-04-17 at 14:41 +0800, Mao Han wrote:
> I'v just spent sometime debuging this. Core dump backtrace on C-SKY
> seems
> can't be supported with current generic routine. DWARF register order is
> different from the order in core notes. The initialization of frame
> registers is totall
Oh, of course, that might be it.
Do you know if when it's open with write permission, changes will be mapped
back to the file?
Thanks,
Sasha
From: Frank Ch. Eigler
Sent: Monday, June 24, 5:06 PM
Subject: Re: Elf64_Phdr
To: Sasha Da Rocha Pinheiro
Cc: elfuti
On Tue, 2019-06-25 at 05:22 +, Sasha Da Rocha Pinheiro wrote:
> Oh, of course, that might be it.
>
> Do you know if when it's open with write permission, changes will be
> mapped back to the file?
That depends on whether it is opened with mmap MAP_PRIVATE
(ELF_C_READ_MMAP_PRIVATE,) or
