Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Daniel Jacobowitz'" <drow@false.org>
Cc: <gdb-patches@sourceware.org>
Subject: [PING] [RFC-v2] Use untested for macscp.exp if no macro information 	generated
Date: Wed, 18 Feb 2009 22:59:00 -0000	[thread overview]
Message-ID: <000001c9921b$cf82d500$6e887f00$@u-strasbg.fr> (raw)
In-Reply-To: <000801c9860c$d5dc8ba0$8195a2e0$@u-strasbg.fr>

I didn't get any feedback on this one.
Should I resend it as a RFA?

Pierre Muller
Pascal language support maintainer for GDB



> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Pierre Muller
> Envoyé : Tuesday, February 03, 2009 3:37 PM
> À : 'Daniel Jacobowitz'
> Cc : gdb-patches@sourceware.org
> Objet : [RFC-v2] Use untested for macscp.exp if no macro information
> generated
> 
> Thanks for your feedback Daniel,
> 
> 
> Here is a new lighter version.
> I finally switch from untested to unsupported,
> which seems closer to reality as it is an
> unsupported feature (of the compiler).
> 
>  Again, the test with  "info source" only works once a source file is
> loaded,
> which is the reason why this test is not put at the very
> start of macscp.exp.
> 
> With that patch,
> doing
> $ make check RUNTESTFLAGS="gdb.base/macscp.exp"
> gives this:
> $ cat gdb.sum
> Test Run By Pierre on Tue Feb  3 15:24:03 2009
> Native configuration is i686-pc-cygwin
> 
>                 === gdb tests ===
> 
> Schedule of variations:
>     unix
> 
> Running target unix
> Running ../../../src/gdb/testsuite/gdb.base/macscp.exp ...
> PASS: gdb.base/macscp.exp: list main
> FAIL: gdb.base/macscp.exp: info macro WHERE after `list main'
> (undefined)
> UNSUPPORTED: gdb.base/macscp.exp: Skipping test because debug
> information
> does n
> ot include macro information.
> 
>                 === gdb Summary ===
> 
> # of expected passes            1
> # of unexpected failures        1
> # of unsupported tests          1
> /usr/local/src/gdbcvs/build/gdb/testsuite/../../gdb/gdb version
> 6.8.50.20090203
> -cvs -nw -nx
> 
> 
> 
> 
> Pierre Muller
> Pascal language support maintainer for GDB
> 
> 
> 
> gdb/testsuite/ChangeLog entry:
> 
> 2009-02-03  Pierre Muller  <muller@ics.u-strasbg.fr>
> 
> 	* gdb.base/macscp.exp (info_macro): Return undefined if
> undefined.
> 	(check_macro): Return 1 if undefined.
> 	If first test fails, check if macro debug information is
> available,
> 	and report unsupported test if no macro information is found.
> 
> 
> Index: gdb/testsuite/gdb.base/macscp.exp
> ===================================================================
> RCS file: /cvs/src/src/gdb/testsuite/gdb.base/macscp.exp,v
> retrieving revision 1.19
> diff -u -p -r1.19 macscp.exp
> --- gdb/testsuite/gdb.base/macscp.exp	3 Jan 2009 05:58:03 -0000
> 	1.19
> +++ gdb/testsuite/gdb.base/macscp.exp	3 Feb 2009 14:24:55 -0000
> @@ -152,7 +152,7 @@ proc info_macro {macro} {
>      switch -exact -- $definition {
>          no-macro-info { return no-macro-info }
>          timeout { return timeout }
> -        undefined -
> +        undefined { return undefined }
>          default {
>              if {[llength $location] >= 1} {
>                  return [concat $location [list $definition]]
> @@ -178,6 +178,10 @@ proc check_macro {macro expected where}
>                  xfail "executable includes no macro debugging
> information"
>                  return 1
>              }
> +	    undefined {
> +		fail "info macro $macro $where (undefined)"
> +		return 1
> +	    }
>              timeout {
>                  fail "info macro $macro $where (timeout)"
>              }
> @@ -199,8 +203,28 @@ proc list_and_check_macro {func macro ex
> 
> 
>  if {[list_and_check_macro main WHERE {macscp1.c {before macscp1_3}}]}
> {
> -    return 0
> +    global verbose
> +    set macro_support "unknown"
> +    send_gdb "info source\n"
> +    gdb_test_multiple "info source" "Test macro information"  {
> +	-re "Includes preprocessor macro info\..*$gdb_prompt $" {
> +	    set macro_support 1
> +	    verbose "Source has macro information"
> +	}
> +	-re "Does not include preprocessor macro info\..*$gdb_prompt $" {
> +	    set macro_support 0
> +	    verbose "Source has no macro information"
> +	}
> +	default {
> +	    warning "couldn't check macro support (no valid response)."
> +	}
> +    }
> +    if {$macro_support == 0} {
> +	unsupported "Skipping test because debug information does not
> include macro information."
> +	return 0
> +    }
>  }
> +
>  list_and_check_macro macscp2_2 WHERE {macscp2.h macscp1.c {before
> macscp2_2}}
>  list_and_check_macro macscp3_2 WHERE {macscp3.h macscp1.c {before
> macscp3_2}}
> 


  reply	other threads:[~2009-02-18 22:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-09 11:37 Results of macscp.exp test on cygwin Pierre Muller
2008-10-09 16:29 ` Tom Tromey
2008-10-09 16:46   ` Pedro Alves
2008-10-09 18:14   ` Daniel Jacobowitz
2008-10-09 20:21     ` Michael Snyder
2008-10-09 22:28       ` Paul Pluzhnikov
2008-10-10 16:04   ` [RFC] " Pierre Muller
2009-01-26  9:13     ` [PING] " Pierre Muller
2009-01-28 13:32       ` [RFC] Use untested for macscp.exp if no macro information generated Pierre Muller
2009-02-01 18:28         ` Daniel Jacobowitz
2009-02-03 14:36           ` [RFC-v2] " Pierre Muller
2009-02-18 22:59             ` Pierre Muller [this message]
2009-02-19  8:20               ` [PING] " Tom Tromey
2009-02-20 10:08                 ` Pierre Muller
2009-05-11 11:30                   ` PING : " Pierre Muller
2009-05-29 23:40                     ` Tom Tromey
2009-05-30  8:04                       ` 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='000001c9921b$cf82d500$6e887f00$@u-strasbg.fr' \
    --to=muller@ics.u-strasbg.fr \
    --cc=drow@false.org \
    --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