[binutils-gdb] ld: Create a new LOAD segment for separate code segment

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

[binutils-gdb] ld: Create a new LOAD segment for separate code segment

sergiodj+buildbot-2
*** TEST RESULTS FOR COMMIT 2888249fc9eb38b6d6e4bd969ce63c26e3753d5e ***

Author: H.J. Lu <[hidden email]>
Branch: master
Commit: 2888249fc9eb38b6d6e4bd969ce63c26e3753d5e

ld: Create a new LOAD segment for separate code segment

When generating separate code LOAD segment, create a new LOAD segment
if the previous section contains text and the current section doesn't
or vice versa:

Elf file type is DYN (Shared object file)
Entry point 0x200020
There are 7 program headers, starting at offset 52

Program Headers:
  Type           Offset   VirtAddr   PhysAddr   FileSiz MemSiz  Flg Align
  LOAD           0x000000 0x00000000 0x00000000 0x00200 0x00200 R   0x200000
  LOAD           0x200000 0x00200000 0x00200000 0x00036 0x00036 R E 0x200000
  LOAD           0x400000 0x00400000 0x00400000 0x00064 0x00064 R   0x200000
  LOAD           0x400f80 0x00600f80 0x00600f80 0x000a0 0x000a0 RW  0x200000
  DYNAMIC        0x400f80 0x00600f80 0x00600f80 0x00080 0x00080 RW  0x4
  GNU_STACK      0x000000 0x00000000 0x00000000 0x00000 0x00000 RW  0x10
  GNU_RELRO      0x400f80 0x00600f80 0x00600f80 0x00080 0x00080 R   0x1

 Section to Segment mapping:
  Segment Sections...
   00     .hash .gnu.hash .dynsym .dynstr .rela.plt
   01     .plt .text
   02     .rodata .eh_frame
   03     .dynamic .got.plt
   04     .dynamic
   05
   06     .dynamic

to prevent fetching or executing data in code pages as instructions.

Also don't put a writable section in a read-only segment if there is a
RELRO segment.

Since code segment is aligned and padded to the maximum page size on
disk, the minimum file size is bigger than the maximum page size which
is 2MB (0x200000):

-rwxr-xr-x 1 hjl hjl 4201932 Jan 10 10:41 libfoo.so

"-z max-page-size=0x1000" can be used to reduce the maximum page size to
4KB (0x1000):

-rwxr-xr-x 1 hjl hjl   15820 Jan 10 10:44 libfoo.so

        PR ld/22393
        * elf.c (_bfd_elf_map_sections_to_segments): When generating
        separate code and read-only data LOAD segments, create a new
        LOAD segment if the previous section contains text and the
        current section doesn't or vice versa.  Don't put a writable
        section in a read-only segment if there is a RELRO segment.
Reply | Threaded
Open this post in threaded view
|

Failures on Fedora-x86_64-native-extended-gdbserver-m32, branch master

sergiodj+buildbot-2
Buildslave:
        fedora-x86-64-4

Full Build URL:
        <http://gdb-build.sergiodj.net/builders/Fedora-x86_64-native-extended-gdbserver-m32/builds/8506>

Commit(s) tested:
        2888249fc9eb38b6d6e4bd969ce63c26e3753d5e

Author(s) (in the same order as the commits):
        H.J. Lu <[hidden email]>

Subject:
        ld: Create a new LOAD segment for separate code segment

Testsuite log (gdb.sum and gdb.log) URL(s):
        <http://gdb-build.sergiodj.net/results/Fedora-x86_64-native-extended-gdbserver-m32/28/2888249fc9eb38b6d6e4bd969ce63c26e3753d5e/>

*** Diff to previous build ***
============================
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=on: cond_bp_target=1: inferior 1 exited
============================


*** Complete list of XFAILs for this builder ***

To obtain the list of XFAIL tests for this builder, go to:

        <http://git.sergiodj.net/?p=gdb-xfails.git;a=blob;f=xfails/Fedora-x86_64-native-extended-gdbserver-m32/xfails/master/xfail;hb=4a056df>

You can also see a pretty-printed version of the list, with more information
about each XFAIL, by going to:

        <http://git.sergiodj.net/?p=gdb-xfails.git;a=blob;f=xfails/Fedora-x86_64-native-extended-gdbserver-m32/xfails/master/xfail.table;hb=4a056df>



Reply | Threaded
Open this post in threaded view
|

Failures on Fedora-x86_64-m64, branch master

sergiodj+buildbot-2
In reply to this post by sergiodj+buildbot-2
Buildslave:
        fedora-x86-64-3

Full Build URL:
        <http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m64/builds/8559>

Commit(s) tested:
        2888249fc9eb38b6d6e4bd969ce63c26e3753d5e

Author(s) (in the same order as the commits):
        H.J. Lu <[hidden email]>

Subject:
        ld: Create a new LOAD segment for separate code segment

Testsuite log (gdb.sum and gdb.log) URL(s):
        <http://gdb-build.sergiodj.net/results/Fedora-x86_64-m64/28/2888249fc9eb38b6d6e4bd969ce63c26e3753d5e/>

*** Diff to previous build ***
============================
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=on: cond_bp_target=0: inferior 1 exited
============================


*** Complete list of XFAILs for this builder ***

To obtain the list of XFAIL tests for this builder, go to:

        <http://git.sergiodj.net/?p=gdb-xfails.git;a=blob;f=xfails/Fedora-x86_64-m64/xfails/master/xfail;hb=293ab64>

You can also see a pretty-printed version of the list, with more information
about each XFAIL, by going to:

        <http://git.sergiodj.net/?p=gdb-xfails.git;a=blob;f=xfails/Fedora-x86_64-m64/xfails/master/xfail.table;hb=293ab64>



Reply | Threaded
Open this post in threaded view
|

Failures on Fedora-x86_64-cc-with-index, branch master

sergiodj+buildbot-2
In reply to this post by sergiodj+buildbot-2
Buildslave:
        fedora-x86-64-4

Full Build URL:
        <http://gdb-build.sergiodj.net/builders/Fedora-x86_64-cc-with-index/builds/8455>

Commit(s) tested:
        2888249fc9eb38b6d6e4bd969ce63c26e3753d5e

Author(s) (in the same order as the commits):
        H.J. Lu <[hidden email]>

Subject:
        ld: Create a new LOAD segment for separate code segment

Testsuite log (gdb.sum and gdb.log) URL(s):
        <http://gdb-build.sergiodj.net/results/Fedora-x86_64-cc-with-index/28/2888249fc9eb38b6d6e4bd969ce63c26e3753d5e/>

*** Diff to previous build ***
============================
PASS -> FAIL: gdb.arch/amd64-disp-step-avx.exp: vex2: xmm0 has expected value before
============================


*** Complete list of XFAILs for this builder ***

To obtain the list of XFAIL tests for this builder, go to:

        <http://git.sergiodj.net/?p=gdb-xfails.git;a=blob;f=xfails/Fedora-x86_64-cc-with-index/xfails/master/xfail;hb=3e07033>

You can also see a pretty-printed version of the list, with more information
about each XFAIL, by going to:

        <http://git.sergiodj.net/?p=gdb-xfails.git;a=blob;f=xfails/Fedora-x86_64-cc-with-index/xfails/master/xfail.table;hb=3e07033>



Reply | Threaded
Open this post in threaded view
|

Failures on Fedora-x86_64-m32, branch master

sergiodj+buildbot-2
In reply to this post by sergiodj+buildbot-2
Buildslave:
        fedora-x86-64-1

Full Build URL:
        <http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/8517>

Commit(s) tested:
        2888249fc9eb38b6d6e4bd969ce63c26e3753d5e

Author(s) (in the same order as the commits):
        H.J. Lu <[hidden email]>

Subject:
        ld: Create a new LOAD segment for separate code segment

Testsuite log (gdb.sum and gdb.log) URL(s):
        <http://gdb-build.sergiodj.net/results/Fedora-x86_64-m32/28/2888249fc9eb38b6d6e4bd969ce63c26e3753d5e/>

*** Diff to previous build ***
============================
new FAIL: gdb.base/corefile.exp: core-file warning-free
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=on: cond_bp_target=1: inferior 1 exited
============================


*** Complete list of XFAILs for this builder ***

To obtain the list of XFAIL tests for this builder, go to:

        <http://git.sergiodj.net/?p=gdb-xfails.git;a=blob;f=xfails/Fedora-x86_64-m32/xfails/master/xfail;hb=93edd57>

You can also see a pretty-printed version of the list, with more information
about each XFAIL, by going to:

        <http://git.sergiodj.net/?p=gdb-xfails.git;a=blob;f=xfails/Fedora-x86_64-m32/xfails/master/xfail.table;hb=93edd57>



Reply | Threaded
Open this post in threaded view
|

Failures on Fedora-i686, branch master

sergiodj+buildbot-2
In reply to this post by sergiodj+buildbot-2
Buildslave:
        fedora-x86-64-2

Full Build URL:
        <http://gdb-build.sergiodj.net/builders/Fedora-i686/builds/8541>

Commit(s) tested:
        2888249fc9eb38b6d6e4bd969ce63c26e3753d5e

Author(s) (in the same order as the commits):
        H.J. Lu <[hidden email]>

Subject:
        ld: Create a new LOAD segment for separate code segment

Testsuite log (gdb.sum and gdb.log) URL(s):
        <http://gdb-build.sergiodj.net/results/Fedora-i686/28/2888249fc9eb38b6d6e4bd969ce63c26e3753d5e/>

*** Diff to previous build ***
============================
new FAIL: gdb.gdb/complaints.exp: breakpoint in captured_command_loop
new FAIL: gdb.gdb/complaints.exp: run until breakpoint at captured_command_loop
new FAIL: gdb.gdb/observer.exp: breakpoint in captured_main
new FAIL: gdb.gdb/observer.exp: run until breakpoint at captured_main
new FAIL: gdb.gdb/python-interrupts.exp: breakpoint in captured_command_loop
new FAIL: gdb.gdb/python-interrupts.exp: run until breakpoint at captured_command_loop
new FAIL: gdb.gdb/python-selftest.exp: breakpoint in captured_command_loop
new FAIL: gdb.gdb/python-selftest.exp: run until breakpoint at captured_command_loop
new FAIL: gdb.gdb/selftest.exp: breakpoint in captured_main
new FAIL: gdb.gdb/selftest.exp: run until breakpoint at captured_main
PASS -> FAIL: gdb.linespec/cpls-abi-tag.exp: test_abi_tag: completion: at tag: tab complete "b test_abi_tag_function[abi:"
PASS -> FAIL: gdb.linespec/cpls-abi-tag.exp: test_abi_tag: completion: at tag: cmd complete "b test_abi_tag_function[abi:"
============================


*** Complete list of XFAILs for this builder ***

To obtain the list of XFAIL tests for this builder, go to:

        <http://git.sergiodj.net/?p=gdb-xfails.git;a=blob;f=xfails/Fedora-i686/xfails/master/xfail;hb=e3bd253>

You can also see a pretty-printed version of the list, with more information
about each XFAIL, by going to:

        <http://git.sergiodj.net/?p=gdb-xfails.git;a=blob;f=xfails/Fedora-i686/xfails/master/xfail.table;hb=e3bd253>



Reply | Threaded
Open this post in threaded view
|

Failures on Fedora-x86_64-native-extended-gdbserver-m64, branch master

sergiodj+buildbot-2
In reply to this post by sergiodj+buildbot-2
Buildslave:
        fedora-x86-64-3

Full Build URL:
        <http://gdb-build.sergiodj.net/builders/Fedora-x86_64-native-extended-gdbserver-m64/builds/8545>

Commit(s) tested:
        2888249fc9eb38b6d6e4bd969ce63c26e3753d5e

Author(s) (in the same order as the commits):
        H.J. Lu <[hidden email]>

Subject:
        ld: Create a new LOAD segment for separate code segment

Testsuite log (gdb.sum and gdb.log) URL(s):
        <http://gdb-build.sergiodj.net/results/Fedora-x86_64-native-extended-gdbserver-m64/28/2888249fc9eb38b6d6e4bd969ce63c26e3753d5e/>

*** Diff to previous build ***
============================
PASS -> FAIL: gdb.arch/amd64-disp-step-avx.exp: vex2: xmm0 has expected value before
new FAIL: gdb.mi/mi-exec-run.exp: inferior-tty=main: mi=main: force-fail=1: run failure detected
new FAIL: gdb.mi/mi-exec-run.exp: inferior-tty=main: mi=separate: force-fail=1: run failure detected
new FAIL: gdb.mi/mi-exec-run.exp: inferior-tty=separate: mi=main: force-fail=1: run failure detected
new FAIL: gdb.mi/mi-exec-run.exp: inferior-tty=separate: mi=separate: force-fail=1: run failure detected
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=off: cond_bp_target=0: inferior 1 exited
============================


*** Complete list of XFAILs for this builder ***

To obtain the list of XFAIL tests for this builder, go to:

        <http://git.sergiodj.net/?p=gdb-xfails.git;a=blob;f=xfails/Fedora-x86_64-native-extended-gdbserver-m64/xfails/master/xfail;hb=f51a767>

You can also see a pretty-printed version of the list, with more information
about each XFAIL, by going to:

        <http://git.sergiodj.net/?p=gdb-xfails.git;a=blob;f=xfails/Fedora-x86_64-native-extended-gdbserver-m64/xfails/master/xfail.table;hb=f51a767>



Reply | Threaded
Open this post in threaded view
|

Failures on Fedora-x86_64-native-gdbserver-m64, branch master

sergiodj+buildbot-2
In reply to this post by sergiodj+buildbot-2
Buildslave:
        fedora-x86-64-4

Full Build URL:
        <http://gdb-build.sergiodj.net/builders/Fedora-x86_64-native-gdbserver-m64/builds/8500>

Commit(s) tested:
        2888249fc9eb38b6d6e4bd969ce63c26e3753d5e

Author(s) (in the same order as the commits):
        H.J. Lu <[hidden email]>

Subject:
        ld: Create a new LOAD segment for separate code segment

Testsuite log (gdb.sum and gdb.log) URL(s):
        <http://gdb-build.sergiodj.net/results/Fedora-x86_64-native-gdbserver-m64/28/2888249fc9eb38b6d6e4bd969ce63c26e3753d5e/>

*** Diff to previous build ***
============================
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=off: cond_bp_target=1: inferior 1 exited
============================


*** Complete list of XFAILs for this builder ***

To obtain the list of XFAIL tests for this builder, go to:

        <http://git.sergiodj.net/?p=gdb-xfails.git;a=blob;f=xfails/Fedora-x86_64-native-gdbserver-m64/xfails/master/xfail;hb=d5466a1>

You can also see a pretty-printed version of the list, with more information
about each XFAIL, by going to:

        <http://git.sergiodj.net/?p=gdb-xfails.git;a=blob;f=xfails/Fedora-x86_64-native-gdbserver-m64/xfails/master/xfail.table;hb=d5466a1>



Reply | Threaded
Open this post in threaded view
|

Failures on Ubuntu-AArch64-native-gdbserver-m64, branch master

sergiodj+buildbot-2
In reply to this post by sergiodj+buildbot-2
Buildslave:
        ubuntu-aarch64-1

Full Build URL:
        <http://gdb-build.sergiodj.net/builders/Ubuntu-AArch64-native-gdbserver-m64/builds/3929>

Commit(s) tested:
        2888249fc9eb38b6d6e4bd969ce63c26e3753d5e

Author(s) (in the same order as the commits):
        H.J. Lu <[hidden email]>

Subject:
        ld: Create a new LOAD segment for separate code segment

Testsuite log (gdb.sum and gdb.log) URL(s):
        <http://gdb-build.sergiodj.net/results/Ubuntu-AArch64-native-gdbserver-m64/28/2888249fc9eb38b6d6e4bd969ce63c26e3753d5e/>

*** Diff to previous build ***
============================
PASS -> KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=on: cond_bp_target=1: inferior 1 exited
============================


*** Complete list of XFAILs for this builder ***

To obtain the list of XFAIL tests for this builder, go to:

        <http://git.sergiodj.net/?p=gdb-xfails.git;a=blob;f=xfails/Ubuntu-AArch64-native-gdbserver-m64/xfails/master/xfail;hb=7b8f22d>

You can also see a pretty-printed version of the list, with more information
about each XFAIL, by going to:

        <http://git.sergiodj.net/?p=gdb-xfails.git;a=blob;f=xfails/Ubuntu-AArch64-native-gdbserver-m64/xfails/master/xfail.table;hb=7b8f22d>



Reply | Threaded
Open this post in threaded view
|

Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, branch master

sergiodj+buildbot-2
In reply to this post by sergiodj+buildbot-2
Buildslave:
        ubuntu-trusty-aarch32-1

Full Build URL:
        <http://gdb-build.sergiodj.net/builders/Ubuntu-AArch32-native-extended-gdbserver-m32/builds/2541>

Commit(s) tested:
        2888249fc9eb38b6d6e4bd969ce63c26e3753d5e

Author(s) (in the same order as the commits):
        H.J. Lu <[hidden email]>

Subject:
        ld: Create a new LOAD segment for separate code segment

Testsuite log (gdb.sum and gdb.log) URL(s):
        <http://gdb-build.sergiodj.net/results/Ubuntu-AArch32-native-extended-gdbserver-m32/28/2888249fc9eb38b6d6e4bd969ce63c26e3753d5e/>

*** Diff to previous build ***
============================
PASS -> FAIL: gdb.base/longjmp.exp: next over patt3
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=6: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=7: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=9: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=10: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=13: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=15: wait for stops
new FAIL: gdb.threads/interrupt-while-step-over.exp: displaced-stepping=off: iter=18: wait for stops
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=off: cmd=next: call_function=0: find current thread
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=off: cmd=next: call_function=0: listed args
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=off: cmd=next: call_function=0: next to increment
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=off: cmd=next: call_function=0: next does not change thread
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=off: cmd=next: call_function=0: current thread advanced - unlocked
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=off: cmd=next: call_function=1: continue to breakpoint: return to loop
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=off: cmd=next: call_function=1: find current thread
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=off: cmd=next: call_function=1: print call_function = 1
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=off: cmd=next: call_function=1: listed args
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=off: cmd=next: call_function=1: next to increment
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=off: cmd=next: call_function=1: other threads ran - unlocked
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=step: cmd=step: continue to breakpoint: return to loop
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=step: cmd=step: find current thread
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=step: cmd=step: print call_function = 0
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=step: cmd=step: listed args
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=step: cmd=step: step to increment
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=step: cmd=next: call_function=0: continue to breakpoint: return to loop
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=step: cmd=next: call_function=0: find current thread
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=step: cmd=next: call_function=0: print call_function = 0
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=step: cmd=next: call_function=0: listed args
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=step: cmd=next: call_function=0: next to increment
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=step: cmd=next: call_function=1: continue to breakpoint: return to loop
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=step: cmd=next: call_function=1: find current thread
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=step: cmd=next: call_function=1: print call_function = 1
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=step: cmd=next: call_function=1: listed args
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=step: cmd=next: call_function=1: next to increment
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=on: cmd=step: continue to breakpoint: return to loop
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=on: cmd=step: find current thread
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=on: cmd=step: print call_function = 0
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=on: cmd=step: listed args
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=on: cmd=step: step to increment
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=on: cmd=next: call_function=0: continue to breakpoint: return to loop
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=on: cmd=next: call_function=0: find current thread
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=on: cmd=next: call_function=0: print call_function = 0
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=on: cmd=next: call_function=0: listed args
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=on: cmd=next: call_function=0: next to increment
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=on: cmd=next: call_function=1: continue to breakpoint: return to loop
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=on: cmd=next: call_function=1: find current thread
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=on: cmd=next: call_function=1: print call_function = 1
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=on: cmd=next: call_function=1: listed args
PASS -> FAIL: gdb.threads/schedlock.exp: schedlock=on: cmd=next: call_function=1: next to increment
============================


*** Complete list of XFAILs for this builder ***

FAILURE TO OBTAIN THE COMMIT FOR THE XFAIL LIST.  PLEASE CONTACT THE BUILDBOT ADMIN.



Reply | Threaded
Open this post in threaded view
|

Failures on Ubuntu-AArch32-native-gdbserver-m32, branch master

sergiodj+buildbot-2
In reply to this post by sergiodj+buildbot-2
Buildslave:
        ubuntu-trusty-aarch32-1

Full Build URL:
        <http://gdb-build.sergiodj.net/builders/Ubuntu-AArch32-native-gdbserver-m32/builds/2523>

Commit(s) tested:
        2888249fc9eb38b6d6e4bd969ce63c26e3753d5e

Author(s) (in the same order as the commits):
        H.J. Lu <[hidden email]>

Subject:
        ld: Create a new LOAD segment for separate code segment

Testsuite log (gdb.sum and gdb.log) URL(s):
        <http://gdb-build.sergiodj.net/results/Ubuntu-AArch32-native-gdbserver-m32/28/2888249fc9eb38b6d6e4bd969ce63c26e3753d5e/>

*** Diff to previous build ***
============================
PASS -> KFAIL: gdb.threads/non-ldr-exit.exp: program exits normally
============================


*** Complete list of XFAILs for this builder ***

To obtain the list of XFAIL tests for this builder, go to:

        <http://git.sergiodj.net/?p=gdb-xfails.git;a=blob;f=xfails/Ubuntu-AArch32-native-gdbserver-m32/xfails/master/xfail;hb=>

You can also see a pretty-printed version of the list, with more information
about each XFAIL, by going to:

        <http://git.sergiodj.net/?p=gdb-xfails.git;a=blob;f=xfails/Ubuntu-AArch32-native-gdbserver-m32/xfails/master/xfail.table;hb=>



Reply | Threaded
Open this post in threaded view
|

Failures on Ubuntu-AArch32-m32, branch master

sergiodj+buildbot-2
In reply to this post by sergiodj+buildbot-2
Buildslave:
        ubuntu-trusty-aarch32-1

Full Build URL:
        <http://gdb-build.sergiodj.net/builders/Ubuntu-AArch32-m32/builds/2542>

Commit(s) tested:
        2888249fc9eb38b6d6e4bd969ce63c26e3753d5e

Author(s) (in the same order as the commits):
        H.J. Lu <[hidden email]>

Subject:
        ld: Create a new LOAD segment for separate code segment

Testsuite log (gdb.sum and gdb.log) URL(s):
        <http://gdb-build.sergiodj.net/results/Ubuntu-AArch32-m32/28/2888249fc9eb38b6d6e4bd969ce63c26e3753d5e/>

*** Diff to previous build ***
============================
PASS -> FAIL: gdb.threads/non-stop-fair-events.exp: signal_thread=2: thread 11 broke out of loop
============================


*** Complete list of XFAILs for this builder ***

To obtain the list of XFAIL tests for this builder, go to:

        <http://git.sergiodj.net/?p=gdb-xfails.git;a=blob;f=xfails/Ubuntu-AArch32-m32/xfails/master/xfail;hb=>

You can also see a pretty-printed version of the list, with more information
about each XFAIL, by going to:

        <http://git.sergiodj.net/?p=gdb-xfails.git;a=blob;f=xfails/Ubuntu-AArch32-m32/xfails/master/xfail.table;hb=>