similar to: [PATCH 0/4] efi: PE header generation fix

On Wed, 27 Nov, at 02:38:28PM, Celelibi wrote: > The value of the field rva_and_sizes_nr is used by OVMF to check the > consistency of the PE file with respect to the field optional_hdr_sz. It > now have the right value. > > Signed-off-by: Celelibi <celelibi at gmail.com> > --- > efi/wrapper.c | 6 +++--- > efi/wrapper.h | 28 ++++++++++++++++------------ > 2

PE headers code_sz and image_sz indicate more or less, the size of the file and the size of the in-memory image. They are now given the right value. In the ELF format, only the program headers are reliable to determine the actually needed part of the file and the in-memory size. The .bss section should always be marked as NOLOAD for ld since its content shouldn't be included into the binary

PE headers code_sz and image_sz indicate more or less, the size of the file and the size of the in-memory image. They are now given the right value. In the ELF format, only the program headers are reliable to determine the actually needed part of the file and the in-memory size. The .bss section should always be marked as NOLOAD for ld since its content shouldn't be included into the binary

There is no need to have a relocation section that nothing points at. The image is still seen as relocatable as long as the Characteristics of the FileHeader do not say otherwise. Moreover, the field base_relocation_table wasn't initialized properly leading to unpredictable bugs. Signed-off-by: Celelibi <celelibi at gmail.com> --- efi/wrapper.c | 28 +++------------------------- 1

In the generated PE file, the section header for the .text section used to address more than the whole file. Starting at offset 0 (before the end of the headers) is illegal and is rejected by OVMF. Giving a size greater than the actual file size is also illegal and rejected. Moreover, the actual data inside the PE file have to be aligned to at least 512 bytes. Hence, .text need to be aligned as

There is no need to have a relocation section that nothing points at. The image is still seen as relocatable as long as the Characteristics of the FileHeader do not say otherwise. Moreover, the field base_relocation_table wasn't initialized properly leading to unpredictable bugs. Signed-off-by: Celelibi <celelibi at gmail.com> --- I'm not 100% positive about the uselessness of the

Does this look okay? : Time: 1:15.50 of 4:13.73, Bitrate: 133.3 How about? : <snip from=ogg123.c> info.u_time = ov_time_total (&vf, -1); /* Seconds with double precision */ gettimeofday (&start_time, NULL); t_min = (long) info.u_time / (long) 60; t_sec = info.u_time - 60 * t_min; while (! eos) { gettimeofday (&cur_time, NULL); c_min = (long)

On Wed, 27 Nov, at 02:38:29PM, Celelibi wrote: > In the generated PE file, the section header for the .text section used > to address more than the whole file. Starting at offset 0 (before the > end of the headers) is illegal and is rejected by OVMF. Giving a size > greater than the actual file size is also illegal and rejected. > > Moreover, the actual data inside the PE file

The value of the field rva_and_sizes_nr is used by OVMF to check the consistency of the PE file with respect to the field optional_hdr_sz. It now have the right value. Signed-off-by: Celelibi <celelibi at gmail.com> --- efi/wrapper.c | 6 +++--- efi/wrapper.h | 28 ++++++++++++++++------------ 2 files changed, 19 insertions(+), 15 deletions(-) diff --git a/efi/wrapper.c b/efi/wrapper.c

The value of the field rva_and_sizes_nr is used by OVMF to check the consistency of the PE file with respect to the field optional_hdr_sz. It now have the right value. Signed-off-by: Celelibi <celelibi at gmail.com> --- efi/wrapper.c | 6 +++--- efi/wrapper.h | 28 ++++++++++++++++------------ 2 files changed, 19 insertions(+), 15 deletions(-) diff --git a/efi/wrapper.c b/efi/wrapper.c

hello, On Mon, 16 Jun 2008, Joey Hess wrote: > klibc cpio segfaults extracting various cpio files. It seems to work for > small files, but fail for larger ones, including the d-i root floppy > image. > > For example: > > joey at kodama:/tmp/empty>wget http://people.debian.org/~joeyh/d-i/images/20080401-09:01/floppy/root.img > joey at kodama:/tmp/empty>zcat

Hello, after splitting a data-frame I want to access the results. Maybe the problem is, that the factor/index is a string... ...or do I miss knowing details of the index-uasge? Please look and help: ======================================= > weblog <- read_weblog("web.log") > > > str(weblog) 'data.frame': 2247 obs. of 18 variables: $ host : Factor w/ 77

Hi! This is the third and last patch. This patch makes the xen kernel buildable on OpenBSD by adding support for ProPolice. ProPolice has been added to standard GCC in version 4.1.x under the name Stack Smashing Protection (SSP). Cheers Christoph _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, I have problem with quota storage information in dovecot-2.2.29 (and newer versions, too - 2.2.30.2). I use FS quota backend. ............................ # 2.2.29.1 (e0b76e3): /etc/dovecot/dovecot.conf # OS: Linux 4.4.68-1 x86_64 mail_plugins = quota plugin { quota = fs:User quota:mount=/poczta:user quota2 = fs:Group quota:mount=/poczta:group } protocol imap {

I've just pushed out a 6.00-pre1 release. This release includes support for booting EFI machines. The code is currently in the alpha stage. Having said that, you should expect most things to work correctly, including things like the graphical menu. Please help test if you can, and if you find any bugs, please report them. To facilitate building different versions of syslinux.efi (32-bit and

W dniu 20.06.2017 o 21:25, Timo Sirainen pisze: > On 20 Jun 2017, at 15.49, Macka <dovecot at macka.pl> wrote: >> Hi, >> >> I have problem with quota storage information in dovecot-2.2.29 (and >> newer versions, too - 2.2.30.2). >> I use FS quota backend. > . >> After upgrade from 2.2.27 to 2.2.29 (newest 2.2.30.2 too), dovecot >> returns

I am cross-compiling rsync 2.6.2 on Linux i386 for Linux ARM. I pass the following to configure: LDSHARED=~/buildroot/build_arm_nofpu/staging_dir/bin/arm-linux-uclibc-gcc CXX=~/buildroot/build_arm_nofpu/staging_dir/bin/arm-linux-uclibc-g++ CC=~/buildroot/build_arm_nofpu/staging_dir/bin/arm-linux-uclibc-gcc AR=~/buildroot/build_arm_nofpu/staging_dir/bin/arm-linux-uclibc-ar

Finally, the Syslinux 6.00 release is out. This release includes support for booting from EFI, both from disk-based media and over the network via PXE. Thanks to everyone who has been testing this out. There are some EFI bugs that I'm aware of, * booting Linux kernels without CONFIG_RELOCATABLE doesn't work * 64-bit syslinux.efi cannot boot 32-bit kernels and vice versa *

Hi, this commit https://github.com/dovecot/core/commit/c9d76e2baf653fa5504d6849e5c1aae32eff3c53 added code which can not be compiled with uclibc-ng 1.0.26 using buildroot: make[3]: Entering directory '/home/bernd/buildroot/br4/output/build/dovecot-2.2.33.2/src/lib-test' /bin/bash ../../libtool --tag=CC --mode=compile

I have a new problem: Register RBP is used in a function foo. (I am not allocating RBP to any virtual register, the instances of RBP in function foo are in the machine code when my register allocator starts.) Function foo calls function bar. Register RBP is not saved across the call, though it is live after the call. Function bar includes a virtual register. The code that I'm using to