From: Fernando Nasser <fnasser@redhat.com>
To: law@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: gdb.base/break.exp fix
Date: Wed, 19 Dec 2001 12:48:00 -0000 [thread overview]
Message-ID: <3C20FD0A.42AD6E46@redhat.com> (raw)
In-Reply-To: <22625.1008794391@porcupine.cygnus.com>
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
prev parent reply other threads:[~2001-12-19 20:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 12:41 law
2001-12-19 12:48 ` Fernando Nasser [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C20FD0A.42AD6E46@redhat.com \
--to=fnasser@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=law@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox