similar to: [PATCH] tests/regressions: Remove executable stack test.

It's not our job to worry about downstream packaging issues ... --- generator/tests.ml | 1 - tests/regressions/Makefile.am | 3 +- tests/regressions/test-noexec-stack.pl | 78 ---------------------------------- tests/regressions/tests.mk | 3 +- 4 files changed, 2 insertions(+), 83 deletions(-) delete mode 100755

It's not our job to worry about downstream packaging issues ... --- generator/tests.ml | 1 - tests/regressions/Makefile.am | 3 +- tests/regressions/test-noexec-stack.pl | 78 ---------------------------------- tests/regressions/tests.mk | 3 +- 4 files changed, 2 insertions(+), 83 deletions(-) delete mode 100755

--- capitests/Makefile.am | 4 ++- capitests/check-noexec-stack.pl | 58 +++++++++++++++++++++++++++++++++++++++ 2 files changed, 61 insertions(+), 1 deletions(-) create mode 100755 capitests/check-noexec-stack.pl diff --git a/capitests/Makefile.am b/capitests/Makefile.am index 71928ec..08466ac 100644 --- a/capitests/Makefile.am +++ b/capitests/Makefile.am @@ -22,13 +22,15 @@

Test case adapted from Hu Zhang's RHBZ#1242853, thanks. --- tests/regressions/Makefile.am | 2 + tests/regressions/rhbz1011907-1165785.sh | 66 ++++++++++++++++++++++++++++++++ 2 files changed, 68 insertions(+) create mode 100755 tests/regressions/rhbz1011907-1165785.sh diff --git a/tests/regressions/Makefile.am b/tests/regressions/Makefile.am index c4f60ae..026987b 100644 ---

Thanks: Dan Berrangé for identifying the problem. --- .gitignore | 1 + src/command.c | 11 +++++++ tests/regressions/Makefile.am | 13 +++++++- tests/regressions/test-big-heap.c | 69 +++++++++++++++++++++++++++++++++++++++ 4 files changed, 93 insertions(+), 1 deletion(-) create mode 100644 tests/regressions/test-big-heap.c diff --git

Hello, I am currently switching to ldd from ld.bfd on a cross-platform embedded project and am facing a behaviour difference when using the same linker scripts with ld.bfd and ldd. Could anybody please give me a more reliable direction I should go with to get the same behaviour from both of the linkers? Target binary format is a 32-bit ELF executable, which is expected to consist of a single RWX

All it did was checking for a libvirt version, which is what libvirt-is-version now does; hence remove the C part, and use guestfish, ignoring the launch failure (as the C test did). --- .gitignore | 1 - tests/regressions/Makefile.am | 21 ------------ tests/regressions/rhbz1044014.c | 69 ---------------------------------------- tests/regressions/rhbz1044014.sh | 12

https://bugzilla.redhat.com/show_bug.cgi?id=1175196 Currently if you write something like LIBGUESTFS_DEBUG=0 or LIBGUESTFS_DEBUG=true then it doesn't do what you probably expect. This patch series fixes that. Rich.

Hallo all, I have the following glm model: f1 <- as.formula(paste("factor(y.fondi)~", "flgsess + segmeta2 + udm + zona.geo + ultimo.prod.", "+flg.a2 + flg.d.na2 + flg.v2 + flg.cc2", " +(flg.a1 + flg.d.na1 + flg.v1 + flg.cc1)^2", " + flg.a2:flg.d.na2 + flg.a2:flg.v2 +

G'day, I am just getting into rsync and have been very impressed with performance and reliability. There is one thing I haven't worked out how to do yet and I haven't found much with several Google sessions or by way of consulting the examples. I am looking for a way to check for (or duplicate) single flag files to and from a remote host (without any dummy spit errors when it is not

Since v4: - More tests have been converted. - Testing local guests fixed. - Drop no-exec-stack test.

Hello all, The lld linker appears to generate extra ELF program headers and thus causes file sizes to be significantly larger than what would get with ld.gold or ld.bfd. # readelf -l test.bfd Elf file type is EXEC (Executable file) Entry point 0x4000b0 There are 2 program headers, starting at offset 64 Program Headers: Type Offset VirtAddr PhysAddr

For v6: This is mainly just a rebase, but I have also added tests in the ocaml/ language bindings directory, and for all the OCaml-written virt tools. Rich.

I've having problems with a BT 2 span ISDN-30/Digium TE205P asterisk setup with outgoing calls not completing and requiring an Asterisk reset to 'unstick' span 1. Sorry this is a bit long but I'm completely out of my depth :-( This system has been in use for some while and I recently upgraded it to asterisk 1.4.24, zaptel 1.4.11 and libpri 1.4.9. I didn't change

v7: The only changes since v6 are those suggested by Pino in the review of v5.

This converts more of the tests (basically everything under tests/) to use the test harness, revealing some problems which have subsequently been fixed. Rich.

Add a simple test which uses scanelf or readelf to detect whether the supermin executable is really not executable. Kind of followup of commit c9f7a7998021e1cbe22a8ec325d43e2bdc3eff5a. --- tests/Makefile.am | 1 + tests/test-execstack.sh | 32 ++++++++++++++++++++++++++++++++ 2 files changed, 33 insertions(+) create mode 100755 tests/test-execstack.sh diff --git a/tests/Makefile.am

I wonder what is correct way to create PT_LOADs when linkerscript is used ? Currently we create new one for each section that changes access flags. But ld seems to do different thing. Imagine we have next sections: .section .AX.1,"ax" .quad 1 .section .A.1,"a" .quad 2 .section .AW.1,"aw" .quad 3 And script: SECTIONS { . = ALIGN(CONSTANT (MAXPAGESIZE)); .AX : {

This patch adds "guestdev=" boot parameter. This boot parameter is used to reassign page-aligned memory resource and bind PCI back driver. Thanks, -- Yuji Shimada. Signed-off-by: Yuji Shimada <shimada-yxb@necst.nec.co.jp> diff -r 4769a6db78f5 -r fcefb8852878 Documentation/kernel-parameters.txt --- a/Documentation/kernel-parameters.txt Thu Dec 25 10:37:52 2008 +0900 +++

I should probably start by saying this patch series isn't ready for review yet. This patch series adds a test harness to libguestfs. It allows us to run the tests outside the ordinary 'make check' path in the build tree. In particular, you can use this to run tests when libguestfs has been installed. 'make check' and the other 'make check-*' rules still work. The