public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, Xavier Roirand <roirand@adacore.com>
Subject: Re: [RFA/doco] (Ada) provide the exception message when hitting an exception catchpoint
Date: Mon, 27 Nov 2017 12:11:00 -0000	[thread overview]
Message-ID: <67cc8f82-e8db-b34c-8da9-38e2a7795444@redhat.com> (raw)
In-Reply-To: <20171125020534.k4zk7ccpuwnzuspc@adacore.com>

On 11/25/2017 02:05 AM, Joel Brobecker wrote:
>> +ERROR: tcl error sourcing /home/pedro/gdb/src/gdb/testsuite/gdb.ada/mi_catch_ex.exp. 
>> +ERROR: can't read "exception_name(",exception-message="foo\.adb:[0-9]+ explicit raise)": variable isn't array 
>> +    while executing
>> +"mi_expect_stop  "breakpoint-hit\",disp=\"keep\",bkptno=\"$any_nb\",exception-name=\"$exception_name(\",exception-message=\"$exception_message)?"  "foo..."
>> +    (procedure "continue_to_exception" line 17)
>> +    invoked from within
>> +"continue_to_exception \
>> +    "CONSTRAINT_ERROR" "foo\\.adb:$decimal explicit raise" \
>> +    "continue until CE caught by all-exceptions catchpoint""
>> +    (file "/home/pedro/gdb/src/gdb/testsuite/gdb.ada/mi_catch_ex.exp" line 106)
>> +    invoked from within
>> +"source /home/pedro/gdb/src/gdb/testsuite/gdb.ada/mi_catch_ex.exp"
>> +    ("uplevel" body line 1)
>> +    invoked from within
>> +"uplevel #0 source /home/pedro/gdb/src/gdb/testsuite/gdb.ada/mi_catch_ex.exp"
>> +    invoked from within
>> +"catch "uplevel #0 source $test_file_name""
> 
> Grumpf. Sorry about that. I'm not sure why it was working for me
> before. I was able to reproduce on a different machine, but noticed
> another error in the process. Attached is a tentative patch. It gives
> me clean results (15 PASSes). Does it work for you?

Yup, works for me.

Thanks,
Pedro Alves

> 
> gdb/testsuite/ChangeLog:
> 
>         * gdb.ada/mi_catch_ex.exp (continue_to_exception): Adjust
>         expected output in gdb_expect call to allow the exception
>         message to be present as well. Fix syntax confusion to avoid
>         TCL thinking that exception_name is an array.
> 

  reply	other threads:[~2017-11-27 12:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-17 21:20 Joel Brobecker
2017-11-24 21:32 ` Joel Brobecker
2017-11-24 21:44   ` Eli Zaretskii
2017-11-24 22:17     ` Joel Brobecker
2017-11-24 23:00 ` Pedro Alves
2017-11-25  2:05   ` Joel Brobecker
2017-11-27 12:11     ` Pedro Alves [this message]
2017-11-27 19:42       ` Joel Brobecker

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=67cc8f82-e8db-b34c-8da9-38e2a7795444@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=roirand@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).