public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin v. Loewis" <martin@mira.isdn.cs.tu-berlin.de>
To: carlo@runaway.xs4all.nl
Cc: egcs@cygnus.com
Subject: Re: Bug?
Date: Sun, 28 Feb 1999 10:32:00 -0000	[thread overview]
Message-ID: <199902281828.TAA10464@mira.isdn.cs.tu-berlin.de> (raw)
In-Reply-To: < 199902281348.OAA03093@jolan.ppro > (message from Carlo Wood onSun, 28 Feb 1999 14:48:29 +0100 (CET))

> Hi all.  Here's another bug that is probably useless to you because
> you can't reproduce it :(.  Nevertheless:

Thanks. This is a known bug. The work-around is to put some global
symbol into the source file. If this still fails, the global symbol
should appear before the include. Eg.

int this_is_debugdebugcheckpoint_cc = 0;

Hope this helps,
Martin

WARNING: multiple messages have this Message-ID
From: "Martin v. Loewis" <martin@mira.isdn.cs.tu-berlin.de>
To: carlo@runaway.xs4all.nl
Cc: egcs@cygnus.com
Subject: Re: Bug?
Date: Sun, 28 Feb 1999 22:53:00 -0000	[thread overview]
Message-ID: <199902281828.TAA10464@mira.isdn.cs.tu-berlin.de> (raw)
Message-ID: <19990228225300.amzTCm9vfjFomrKUrkbBvTtcDPk9bzcPHkIe7fJI1SU@z> (raw)
In-Reply-To: <199902281348.OAA03093@jolan.ppro>

> Hi all.  Here's another bug that is probably useless to you because
> you can't reproduce it :(.  Nevertheless:

Thanks. This is a known bug. The work-around is to put some global
symbol into the source file. If this still fails, the global symbol
should appear before the include. Eg.

int this_is_debugdebugcheckpoint_cc = 0;

Hope this helps,
Martin

  parent reply	other threads:[~1999-02-28 10:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-28  5:51 Bug? Carlo Wood
     [not found] ` < 199902281348.OAA03093@jolan.ppro >
1999-02-28 10:32   ` Martin v. Loewis [this message]
1999-02-28 22:53     ` Bug? Martin v. Loewis
1999-02-28 22:53 ` Bug? Paul Derbyshire
1999-02-28 22:53 ` Bug? Carlo Wood
2004-07-11 16:37 bug? Katsuya TANAKA
2004-07-12 11:35 ` bug? Dave Korn
2004-12-12  0:58 Bug? Sam Lauber
2004-12-12  1:49 ` Bug? Giovanni Bajo
2004-12-12  3:24 ` Bug? Aaron W. LaFramboise

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=199902281828.TAA10464@mira.isdn.cs.tu-berlin.de \
    --to=martin@mira.isdn.cs.tu-berlin.de \
    --cc=carlo@runaway.xs4all.nl \
    --cc=egcs@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).