Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: "'gdb-patches'" <gdb-patches@sourceware.org>
Subject: Re: [RFA PATCH 3/3] Testcase for pascal/17815
Date: Thu, 22 Jan 2015 12:46:00 -0000	[thread overview]
Message-ID: <54C0F10E.60402@redhat.com> (raw)
In-Reply-To: <54afff6b.ee8d440a.16ee.ffffb424SMTPIN_ADDED_BROKEN@mx.google.com>

Thanks for adding the test case.

On 01/09/2015 04:18 PM, Pierre Muller wrote:
>   This adds the testcase for pascal/17815 bug report.
> 
> 
> gdb/testsuite/Changelog entry:
> 
> 2015-01-09  Pierre Muller  <muller@sourceware.org>
> 
> 	gdb.pascal/gdb17815.pas: New file.
> 	gdb.pascal/gdb17815.exp: New file.

Missing '*'.

Can you please pick a more descriptive name for the file?
One that suggests what's being tested, rather than a bug
number is ideal.  E.g., gdb.pascal/case-insensitive.{exp|pas}.

> +load_lib "pascal.exp"
> +
> +standard_testfile .pas
> +
> +if {[gdb_compile_pascal "${srcdir}/${subdir}/${srcfile}" "${binfile}"
> executable [list debug class]] != "" } {
> +    untested $testfile.exp
> +    return -1
> +}
> +
> +clean_restart ${testfile}
> +set bp_location [gdb_get_line_number "set breakpoint here"]
> +
> +if { [gdb_breakpoint ${srcfile}:${bp_location}] } {
> +    pass "setting breakpoint"
> +}
> +
> +# Verify that "start" lands inside the right procedure.
> +if { [gdb_start_cmd] < 0 } {
> +    untested start
> +    return -1
> +}
> +
> +gdb_test "" ".* at .*${srcfile}.*" "start"
> +gdb_test "continue" ""

I won't object to this, given that it seems like all
pascal tests do it, but I'll note that it's best to avoid
gdb_start_cmd unless we're really testing the "start" command,
as otherwise the test won't run against gdbserver
(try --target_board=native-gdbserver).  Doesn't runto_main
work?

> +# We are now inside CHECK method

Could you add a period at end of sentences?  Here and throughout.

> +gdb_test "p X" " = 67"
> +gdb_test "p B.X" " = -1"
> +# As A is global, we can also check it global value
                                       ^^
Should be "its".

Or, "check its value"?  What's a _global_ value?

> +gdb_test "p A.X" " = 67"
> +gdb_test "p Y" " = 33"
> +gdb_test "p Y" " = 33"

Duplicate test here.  Please try the recipe at:

 https://sourceware.org/gdb/wiki/GDBTestcaseCookbook#Make_sure_test_messages_are_unique

Thanks,
Pedro Alves


  parent reply	other threads:[~2015-01-22 12:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <54ae4586.01e3440a.7b06.fffff844SMTPIN_ADDED_BROKEN@mx.google.com>
2015-01-08 10:48 ` [RFA] Fix pascal behavior for class fields Pedro Alves
2015-01-08 13:01   ` Pierre Muller
     [not found]   ` <54ae7f9f.c323460a.36ed.ffffff30SMTPIN_ADDED_BROKEN@mx.google.com>
2015-01-08 13:41     ` Pedro Alves
2015-01-08 14:15       ` gdb-patches RFA: " Pierre Muller
     [not found]       ` <54ae911b.85e3440a.1d96.5ffdSMTPIN_ADDED_BROKEN@mx.google.com>
2015-01-09 10:52         ` Pedro Alves
2015-01-09 10:55           ` Pedro Alves
2015-01-09 16:16           ` [RFA 0/3] Fix pascal behavior for class fields with testcase Pierre Muller
2015-01-09 16:18             ` [RFA PATCH 2/3] Add debug-stabs debug-dwarf and class option for pascal compiler Pierre Muller
2015-02-04 23:37             ` [RFA 0/3 V4] Fix pascal behavior for class fields with testcase Pierre Muller
2015-02-15  6:59               ` PING " Pierre Muller
2015-04-07 20:06                 ` PING^2 " Pierre Muller
     [not found]               ` <54e043b2.626ec20a.0c59.ffffaeacSMTPIN_ADDED_BROKEN@mx.google.com>
2015-04-20  6:00                 ` PING " Doug Evans
2015-04-21 20:33                   ` Pierre Muller
2015-01-09 16:16           ` [RFA PATCH 1/3] Remember the case pattern that allowed finding a field of this Pierre Muller
2015-01-23  7:30             ` [RFA PATCH 1/3 V3] " Pierre Muller
2015-02-04 23:37               ` [RFA PATCH 1/3 V4] " Pierre Muller
2015-01-09 16:18           ` [RFA PATCH 3/3] Testcase for pascal/17815 Pierre Muller
     [not found]           ` <54afff61.6790420a.0fa7.4f63SMTPIN_ADDED_BROKEN@mx.google.com>
2015-01-10  0:45             ` [RFA PATCH 2/3] Add debug-stabs debug-dwarf and class option for pascal compiler Doug Evans
2015-01-10  0:55               ` Pierre Muller
     [not found]               ` <54b07891.01b3c20a.2a7b.ffff9f96SMTPIN_ADDED_BROKEN@mx.google.com>
2015-01-10 21:23                 ` Doug Evans
2015-01-14 15:04                   ` [RFA PATCH 2/3 V2] Add "class" " Pierre Muller
     [not found]                   ` <54b6858f.a287440a.5b61.ffff9ef0SMTPIN_ADDED_BROKEN@mx.google.com>
2015-01-22 12:49                     ` Pedro Alves
2015-01-23  5:21                       ` [RFA PATCH 2/3 V3] " Pierre Muller
2015-01-23 11:55                         ` Pedro Alves
2015-02-04 23:37                           ` [RFA PATCH 2/3 V4] " Pierre Muller
     [not found]           ` <54afff6b.ee8d440a.16ee.ffffb424SMTPIN_ADDED_BROKEN@mx.google.com>
2015-01-22 12:46             ` Pedro Alves [this message]
2015-01-23  7:16               ` [RFA PATCH 3/3 V3] Testcase for pascal/17815 Pierre Muller
2015-01-23 12:29                 ` Pedro Alves
2015-02-04 23:37                   ` [RFA PATCH 3/3 V4] " Pierre Muller

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=54C0F10E.60402@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    /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