[Bug breakpoints/12466] New: Some GDB tests fail, when "breakpointalways-inserted" is set to "on"

["maxim2405 at gmail dot com" <sourceware-bugzilla at sourceware dot org>]

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

           Summary: Some GDB tests fail, when "breakpoint always-inserted"
                    is set to "on"
           Product: gdb
           Version: 7.1
            Status: NEW
          Severity: normal
          Priority: P2
         Component: breakpoints
        AssignedTo: unassigned@sourceware.org
        ReportedBy: maxim2405@gmail.com


In Xtensa GDB 7.1, I modified the default in breakpoint.c :

305c305
< static const char *always_inserted_mode = always_inserted_auto;
---
> static const char *always_inserted_mode = always_inserted_on;

It caused a regression on some GDB tests :

(gdb) FAIL: gdb.base/break.exp: finish from called function
(gdb) FAIL: gdb.base/callfuncs.exp: finish from call dummy breakpoint 
returns correct value
FAIL: gdb.base/callfuncs.exp: finish after stop in call dummy preserves 
register contents
FAIL: gdb.base/callfuncs.exp: return after stop in call dummy preserves 
register contents
(gdb) FAIL: gdb.base/callfuncs.exp: Finish from nested call level 4
(gdb) FAIL: gdb.base/callfuncs.exp: backtrace after finish from nested 
call level 4
(gdb) FAIL: gdb.base/callfuncs.exp: Finish from nested call level 3
(gdb) FAIL: gdb.base/callfuncs.exp: backtrace after finish from nested 
call level 3
(gdb) FAIL: gdb.base/callfuncs.exp: Finish from nested call level 2
(gdb) FAIL: gdb.base/callfuncs.exp: backtrace after finish from nested 
call level 2
(gdb) FAIL: gdb.base/callfuncs.exp: Finish from nested call level 1
FAIL: gdb.base/callfuncs.exp: nested call dummies preserve register contents
(gdb) FAIL: gdb.base/sepdebug.exp: finish from called function

The target agent uses z/Z packets to handle breakpoints.

I don't know, whether it's applicable to GDB 7.2, and GDB 7.2.90+.

-- 
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.