gdb.base/break.exp fix

gdb.base/break.exp fix

[law]

Inferior calls on HP's typically go through some trampoline code (sr4export)
in the inferior before reaching the target function.

These trampolines will show up in a backtrace if we're in a called function.

break.exp knows about these trampolines, but apparently some minor tweaks
have been made to the frame output code when doing a backtrace.  While
most of the code in break.exp was suitably updated, there is one case for
HPs that wasn't updated.

Basically this replaces "$hex in marker2" with
                         ($hex in )?


	* gdb.base/break.exp: Fix HP specific search string when testing
	backtracing in a called function.

Index: break.exp
===================================================================
RCS file: /cvs/cvsfiles/devo/gdb/testsuite/gdb.base/break.exp,v
retrieving revision 1.62
diff -c -3 -p -r1.62 break.exp
*** break.exp	2001/03/26 19:55:23	1.62
--- break.exp	2001/12/19 20:33:24
*************** gdb_expect {
*** 592,598 ****
  #
  send_gdb "bt\n"
  gdb_expect {
!     -re "#0\[ \t\]*$hex in marker2.*:4\[49\]\r\n#1.*_sr4export.*$gdb_prompt 
$"\
              {pass "backtrace while in called function"}
      -re "#0\[ \t\]*($hex in )?marker2.*:4\[49\]\r\n#1.*function called from 
gdb.*$gdb_prompt $"\
  	    {pass "backtrace while in called function"}
--- 592,598 ----
  #
  send_gdb "bt\n"
  gdb_expect {
!     -re "#0\[ \t\]*($hex in )?marker2.*:4\[49\]\r\n#1.*_sr4export.*$gdb_promp
t $"\
              {pass "backtrace while in called function"}
      -re "#0\[ \t\]*($hex in )?marker2.*:4\[49\]\r\n#1.*function called from 
gdb.*$gdb_prompt $"\
  	    {pass "backtrace while in called function"}

Re: gdb.base/break.exp fix

[Fernando Nasser]

This one is clearly omitted in the previous changes.

You can check it in as an obvious fix.

Regards,
Fernando

law@redhat.com wrote:
> 
> Inferior calls on HP's typically go through some trampoline code (sr4export)
> in the inferior before reaching the target function.
> 
> These trampolines will show up in a backtrace if we're in a called function.
> 
> break.exp knows about these trampolines, but apparently some minor tweaks
> have been made to the frame output code when doing a backtrace.  While
> most of the code in break.exp was suitably updated, there is one case for
> HPs that wasn't updated.
> 
> Basically this replaces "$hex in marker2" with
>                          ($hex in )?
> 
>         * gdb.base/break.exp: Fix HP specific search string when testing
>         backtracing in a called function.
> 
> Index: break.exp
> ===================================================================
> RCS file: /cvs/cvsfiles/devo/gdb/testsuite/gdb.base/break.exp,v
> retrieving revision 1.62
> diff -c -3 -p -r1.62 break.exp
> *** break.exp   2001/03/26 19:55:23     1.62
> --- break.exp   2001/12/19 20:33:24
> *************** gdb_expect {
> *** 592,598 ****
>   #
>   send_gdb "bt\n"
>   gdb_expect {
> !     -re "#0\[ \t\]*$hex in marker2.*:4\[49\]\r\n#1.*_sr4export.*$gdb_prompt
> $"\
>               {pass "backtrace while in called function"}
>       -re "#0\[ \t\]*($hex in )?marker2.*:4\[49\]\r\n#1.*function called from
> gdb.*$gdb_prompt $"\
>             {pass "backtrace while in called function"}
> --- 592,598 ----
>   #
>   send_gdb "bt\n"
>   gdb_expect {
> !     -re "#0\[ \t\]*($hex in )?marker2.*:4\[49\]\r\n#1.*_sr4export.*$gdb_promp
> t $"\
>               {pass "backtrace while in called function"}
>       -re "#0\[ \t\]*($hex in )?marker2.*:4\[49\]\r\n#1.*function called from
> gdb.*$gdb_prompt $"\
>             {pass "backtrace while in called function"}

-- 
Fernando Nasser
Red Hat - Toronto                       E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9