This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug gdb/14971] Failures in gdb.base/longjmp.exp


http://sourceware.org/bugzilla/show_bug.cgi?id=14971

Maciej W. Rozycki <macro@linux-mips.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|x86_64                      |x86_64-linux-gnu,
                   |                            |i686-linux-gnu,
                   |                            |mips-linux-gnu,
                   |                            |powerpc-linux-gnu
                 CC|                            |macro@linux-mips.org

--- Comment #11 from Maciej W. Rozycki <macro@linux-mips.org> ---
I can also see these failures with i686-linux-gnu, mips-linux-gnu and
powerpc-linux-gnu targets, as follows.  The version of glibc used is
2.18, and GCC is 4.8.1 in all the cases.

-------------------------------------------------------------------------
i686 log:

(gdb) PASS: gdb.base/longjmp.exp: next to longjmp (1)
next
Warning:
Cannot insert breakpoint 0.
Cannot access memory at address 0xd840b016

0xb7e55bd1 in __libc_siglongjmp (env=0x8049ae0 <env>, val=1) at longjmp.c:28
28        longjmps++;
(gdb) FAIL: gdb.base/longjmp.exp: next over longjmp(1)

and:

(gdb) PASS: gdb.base/longjmp.exp: next over setjmp (2)
next
Warning:
Cannot insert breakpoint 0.
Cannot access memory at address 0xd8402416

0xb7e55bd1 in __libc_siglongjmp (env=0x8049ae0 <env>, val=1) at longjmp.c:28
28        longjmps++;
(gdb) FAIL: gdb.base/longjmp.exp: next over call_longjmp (2)

and:

(gdb) PASS: gdb.base/longjmp.exp: continue to breakpoint at pattern 3 start
next
Warning:
Cannot insert breakpoint 0.
Cannot access memory at address 0xd8432c16

0xb7e55bd1 in __libc_siglongjmp (env=0x8049ae0 <env>, val=1) at longjmp.c:28
28        longjmps++;
(gdb) FAIL: gdb.base/longjmp.exp: next over patt3

-------------------------------------------------------------------------
MIPS log, n32 only (o32 and n64 ABIs work all right):

(gdb) PASS: gdb.base/longjmp.exp: next to longjmp (1)
next
Warning:
Cannot insert breakpoint 0.
Cannot access memory at address 0x0

0x77db3c64 in __libc_siglongjmp (env=0x10010c50 <env>, val=1) at longjmp.c:28
28        longjmps++;
(gdb) FAIL: gdb.base/longjmp.exp: next over longjmp(1)

and:

(gdb) PASS: gdb.base/longjmp.exp: next over setjmp (2)
next
Warning:
Cannot insert breakpoint 0.
Cannot access memory at address 0x0

0x77db3c64 in __libc_siglongjmp (env=0x10010c50 <env>, val=1) at longjmp.c:28
28        longjmps++;
(gdb) FAIL: gdb.base/longjmp.exp: next over call_longjmp (2)

and:

(gdb) PASS: gdb.base/longjmp.exp: continue to breakpoint at pattern 3 start
next
Warning:
Cannot insert breakpoint 0.
Cannot access memory at address 0x0

0x77db3c64 in __libc_siglongjmp (env=0x10010c50 <env>, val=1) at longjmp.c:28
28        longjmps++;
(gdb) FAIL: gdb.base/longjmp.exp: next over patt3

-------------------------------------------------------------------------
PowerPC log:

(gdb) PASS: gdb.base/longjmp.exp: next to longjmp (1)
next
57            resumes++;
(gdb) FAIL: gdb.base/longjmp.exp: next over longjmp(1)

and:

(gdb) PASS: gdb.base/longjmp.exp: next over setjmp (2)
next

Breakpoint 5, main () at .../gdb/testsuite/gdb.base/longjmp.c:73
73        i = 2; /* miss_step_2 */
(gdb) FAIL: gdb.base/longjmp.exp: next over call_longjmp (2)

-------------------------------------------------------------------------
x86-64 log (for a reference):

(gdb) PASS: gdb.base/longjmp.exp: next to longjmp (1)
next
56            resumes++;
(gdb) FAIL: gdb.base/longjmp.exp: next over longjmp(1)

and:

(gdb) PASS: gdb.base/longjmp.exp: next over setjmp (2)
next

Breakpoint 5, main () at .../gdb/testsuite/gdb.base/longjmp.c:72
72        i = 2; /* miss_step_2 */
(gdb) FAIL: gdb.base/longjmp.exp: next over call_longjmp (2)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]