From: Andrew Cagney <ac131313@redhat.com>
To: David Carlton <carlton@kealia.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] Recover from struct-return internal errors
Date: Thu, 20 Nov 2003 18:44:00 -0000 [thread overview]
Message-ID: <3FBD0B8A.7060108@redhat.com> (raw)
In-Reply-To: <yf2zneqlwlf.fsf@hawaii.kealia.com>
> On Thu, 20 Nov 2003 13:07:18 -0500, Andrew Cagney <ac131313@redhat.com> said:
>
>
>> + -re "A problem internal to GDB has been detected" {
>> + fail "${test} (GDB internal error 1)"
>> + gdb_internal_error_resync
>> + }
>
>
> Could you get rid of some of these by using gdb_test_multiple instead
> of send_gdb/gdb_expect? I haven't looked at structs.exp in detail, so
> I don't have any idea how possible that might be.
I've not really looked at gdb_test_multiple either so I guess we're even
:-) I do know that I can't use "gdb_test" as additional processing is
required dependant on the output.
Andrew
next prev parent reply other threads:[~2003-11-20 18:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 18:07 Andrew Cagney
2003-11-20 18:32 ` David Carlton
2003-11-20 18:44 ` Andrew Cagney [this message]
2003-11-20 18:50 ` Daniel Jacobowitz
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=3FBD0B8A.7060108@redhat.com \
--to=ac131313@redhat.com \
--cc=carlton@kealia.com \
--cc=gdb-patches@sources.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