Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Matt Rice <ratmice@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: gdb.objc/objcdecode.exp test error..
Date: Thu, 24 Sep 2009 06:48:00 -0000	[thread overview]
Message-ID: <8ba6bed40909232348j47027093of7a2bafb8120e5ce@mail.gmail.com> (raw)
In-Reply-To: <20090923231317.GA18470@adacore.com>

On Wed, Sep 23, 2009 at 4:13 PM, Joel Brobecker <brobecker@adacore.com> wrote:
> Matt,
>
>> attached are new tests, and patches for the bug,
>
> I'm only going to look at the testcase patch for now, since it appears
> that the code patches are not ready yet (they fix your issues, but
> at the price of breaking other things, right?). We can work on the
> code patches separately (but, if you don't mind, summarize again what
> the issues are all about, because i'm having a tough time going through
> the scattered emails).

Thats fine

> 2009-03-05  Matt Rice  <ratmice@gmail.com>
>
>        * gdb.objc/objcdecode.exp: Set the multiple symbols found behaviour
>        to ask for the original test. Add tests for the multiple symbols
>        found behaviour of all.
>
>> +do_objc_tests
>
> I know it's not your fault, but it's definitely a misleading name for
> a routine that simple restarts the debugger... Would you mind renaming
> it to something more meaningful? I noticed also that a couple of global
> declarations are not referenced from that routine, and so can be
> removed: objdir and gdb_prompt.
>
> Thanks! :)

np, this is also duplicated in the 2 .exp files,
i should figure out if i can somehow include it from the gdb.objc?

>> +gdb_test "set multiple-symbols all after main" ""
>
> Uh oh, looks like you merged the command being sent to GDB with
> the description of the test :)

oops,

>> +gdb_test_multiple "break multipleDef" $name \
>> +{
>> +  -re "Breakpoint \[0-9\]+ at 0x\[0-9a-f\]+: file .*\r\nBreakpoint \[0-9\]+ at 0x\[0-9a-f\]+: file .*\r\n$gdb_prompt $" { pass $name }
>> +  -re ".*$gdb_prompt $"   { fail $name }
>> +}
>
> The following can be simplified into a simple call to gdb_test, no?
> Also, please consider adding a call to setup_kfail if we expect
> the test to fail with the current sources.  This is true of most if not
> all the tests that are you adding.
>

yeah, I tried to fix all of these in the patch,
there are a couple gdb_test_multiple's left that looks like they need to be.

I also added the setup_kfails, adjusted the existing kfails to use the
bugzilla #.
I will try to remember to go through grep and look for more in testsuite/

well, theres a lot of tests that pass that just involve various setup
for the tests which fail, i think ideally, these would not be tests,
but e.g. if i just do send_gdb
I seem to run into lots of timing issues, i just kfailed the ones that do fail.

ChangeLog is in the git patch header.

> The call to gdb_exit before do_objc_tests is unnecessary.

k

>> +gdb_exit
>> +return 0
>
> I don't think that this is necessary. All scripts do a little bit of
> cleanup before starting the meat of the testcase, so let's not do double
> pollution...

k


  reply	other threads:[~2009-09-24  6:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-06  1:31 Matt Rice
2009-03-06 17:33 ` Joel Brobecker
2009-03-06 19:13   ` Pedro Alves
2009-03-07 12:07     ` Matt Rice
2009-03-08 14:16       ` Matt Rice
2009-03-09  2:10         ` Matt Rice
2009-09-11 11:43           ` Matt Rice
2009-09-24  0:53             ` Joel Brobecker
2009-09-24  8:24               ` Matt Rice
2009-09-24 18:28                 ` Tom Tromey
2009-09-24 22:07                   ` Matt Rice
2009-09-24 22:29                 ` Matt Rice
2009-09-24 22:51                   ` Matt Rice
2009-09-25  4:03               ` Matt Rice
2009-10-13  0:44               ` Tom Tromey
2009-10-14  1:59                 ` Joel Brobecker
2009-09-23 23:13         ` Joel Brobecker
2009-09-24  6:48           ` Matt Rice [this message]
2009-09-24 16:41             ` Joel Brobecker
2009-09-24 17:31               ` Joel Brobecker
2009-09-24 17:41               ` Joel Brobecker
2009-09-24 16:52             ` 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=8ba6bed40909232348j47027093of7a2bafb8120e5ce@mail.gmail.com \
    --to=ratmice@gmail.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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