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: Re: [PATCH RFA] gdb.base/signals.exp: explicitly set count = 0
Date: Fri, 16 Mar 2001 01:08:00 -0000	[thread overview]
Message-ID: <3AB1D7C1.20CED9EC@axis.com> (raw)
In-Reply-To: <3AB0D1C8.B42213EF@redhat.com>

Fernando Nasser wrote:
> 
> Orjan Friberg wrote:
> >
> > 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?
> >
> 
> Yes.
> 

Committed.  Thanks.

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


      reply	other threads:[~2001-03-16  1:08 UTC|newest]

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

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=3AB1D7C1.20CED9EC@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