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] New: Failures in gdb.base/longjmp.exp


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

             Bug #: 14971
           Summary: Failures in gdb.base/longjmp.exp
           Product: gdb
           Version: HEAD
            Status: NEW
          Keywords: testsuite
          Severity: normal
          Priority: P2
         Component: gdb
        AssignedTo: unassigned@sourceware.org
        ReportedBy: dblaikie@gmail.com
    Classification: Unclassified
              Host: Ubuntu (Lucid)
            Target: x86_64


Long jump testing seems to be incorrect - possibly due to both test and product
bugs. In ToT (using git) and 7.5 using both Clang (ToT) and GCC (4.7 & 4.4).
The failures I'm seeing are:

FAIL: gdb.base/longjmp.exp: next over longjmp(1)
FAIL: gdb.base/longjmp.exp: next over call_longjmp (2)

In the first case, when 'next'ing over a longjmp call, gdb stops on the first
line of the else block (from an "if (setjmp(...) == 0)") when the test was
expecting to jump to the line that calls & tests setjmp.

In the second case, when 'next'ing over a call to a function that longjmps
across function boundaries, gdb stops at the next breakpoint, not at the next
statement of or after the setjmp call.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- 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]