Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Orjan Friberg <orjan.friberg@axis.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH RFA] gdb.base/signals.exp: explicitly set count = 0
Date: Thu, 15 Mar 2001 05:54:00 -0000	[thread overview]
Message-ID: <3AB0C976.53755DF7@axis.com> (raw)

gdb.base/signals.exp runs the main function in signals.c twice. 
signal.c contains a static variable count which is initialized to 0. 
The second time the main function is run, the test case relies on count
being 0, which depends on how runto_main is implemented for the target. 
My target does a simple "jump *main", which obviously doesn't
re-initialize count to 0.  This patch sets count to 0 explicitly.

Ok to commit?

2001-03-15  Orjan Friberg  <orjanf@axis.com>

	* gdb.base/signals.exp: Set count to 0 explicitly.


Index: signals.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/signals.exp,v
retrieving revision 1.2
diff -c -3 -p -r1.2 signals.exp
*** signals.exp 2001/03/06 08:21:51     1.2
--- signals.exp 2001/03/15 13:35:40
*************** gdb_expect {
*** 370,375 ****
--- 370,378 ----
  }
  
  if [runto_main] then {
+     # Since count is a static variable outside main, runto_main
+     # is no guarantee that count will be 0 at this point.
+     gdb_test "set variable count = 0" ""
      gdb_test "break handler if 0" "Breakpoint \[0-9\]+ .*"
      gdb_test "set \$handler_breakpoint_number = \$bpnum" ""
  

-- 
Orjan Friberg              E-mail: orjan.friberg@axis.com
Axis Communications AB     Phone:  +46 46 272 17 68


             reply	other threads:[~2001-03-15  5:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-15  5:54 Orjan Friberg [this message]
2001-03-15  6:32 ` Fernando Nasser
2001-03-16  1:08   ` Orjan Friberg

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=3AB0C976.53755DF7@axis.com \
    --to=orjan.friberg@axis.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