public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Dave Korn" <dave.korn@artimi.com>
To: <cygwin@cygwin.com>
Subject: RE: cygheap base mismatch detected
Date: Thu, 16 Feb 2006 18:08:00 -0000	[thread overview]
Message-ID: <007801c63323$77c6b160$a501a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <B7632F7D9BD7B04B94B475272FAD530805704C8E@elschivexch01.elsevier.com>

On 16 February 2006 07:17, Dill, Jens (END-CHI) wrote:


> Unfortunately for me, (e) is impractical.  It's not clear whether
> it is my source code or CygWin's that I need to fix, 

 Have you actually *tried* this application of yours under Cygwin and
discovered that it indeed *is* one of the rare ones that actually runs into
this problem, or are you getting your knickers in a twist over some entirely
theoretical issue that may just as likely never happen?

> My project time frame doesn't allow for that.   If I read Dave Korn's
> posting correctly (along with the others who talk about adjusting the
> sizes of Fortran arrays to fix the problem)

  *Why* are you relying on information that is 12 to 18 months out of date?
There's been quite a few check-ins to the cygwin cvs in that period, and in
case you haven't noticed, we haven't had anyone here running into that problem
recently, and some of the fortran people said that one of the fixes Corinna
made _ages_ ago now had solved the problem in their experience, so perhaps you
should stop hoping to divine the truth from a priori first principles and
outdated mailing-list-posts, and get a bit _empirical_ about it?


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  parent reply	other threads:[~2006-02-16 18:04 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-16  8:40 Dill, Jens (END-CHI)
2006-02-16 17:57 ` Christopher Faylor
2006-02-16 18:08 ` Dave Korn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-03-02  8:14 ignace danneels
2018-03-02  9:39 ` Marco Atzeri
2012-07-18  0:03 Andrew DeFaria
2012-07-18  1:56 ` Reini Urban
2012-07-18  2:37   ` Andrew DeFaria
2012-07-18 15:04     ` Reini Urban
2012-07-18 18:16       ` Andrew DeFaria
2012-07-18 18:38         ` Earnie Boyd
2012-07-18 19:03           ` Andrew DeFaria
2012-02-29 21:19 Charles Wilson
2012-02-29 23:23 ` marco atzeri
2012-03-01  5:56 ` Heiko Elger
2012-03-01  7:03   ` marco atzeri
2012-03-01 10:25   ` Corinna Vinschen
2012-03-01 10:52 ` Corinna Vinschen
2012-03-01 10:59   ` marco atzeri
2012-03-01 12:15     ` Corinna Vinschen
2012-03-01 22:44       ` Charles Wilson
2012-03-02  9:00         ` Corinna Vinschen
2012-03-02 17:11           ` Charles Wilson
2006-02-21 17:40 Dill, Jens (END-CHI)
2006-02-21 16:10 Dill, Jens (END-CHI)
2006-02-21 16:37 ` Brian Dessent
2006-02-21 19:18 ` Yitzchak Scott-Thoennes
2006-02-19  3:34 Dill, Jens (END-CHI)
2006-02-19 18:41 ` Yitzchak Scott-Thoennes
2006-02-20  5:26 ` Mark Geisert
2006-02-20  5:36   ` Christopher Faylor
2006-02-21 21:56 ` Jason Tishler
2006-02-17 22:56 Dill, Jens (END-CHI)
2006-02-17 22:33 Dill, Jens (END-CHI)
2006-02-18 14:33 ` Mark Geisert
2006-02-17 17:43 Dill, Jens (END-CHI)
2006-02-16 23:45 Dill, Jens (END-CHI)
2006-02-17 10:23 ` Dave Korn
2006-02-16 22:05 Dill, Jens (END-CHI)
2006-02-16 19:38 Dill, Jens (END-CHI)
2006-02-16 20:06 ` Chris Taylor
2006-02-16 18:36 Dill, Jens (END-CHI)
2006-02-16 19:50 ` Dave Korn
2005-04-07 10:35 Andreas Heckel
2005-04-07 13:25 ` Dave Korn
2006-02-15 23:49   ` Jens Dill
2006-02-15 23:58     ` Christopher Faylor
2006-02-16 10:42     ` Dave Korn
2005-04-08  0:10 ` Mark Hadfield
2005-04-08  7:35   ` Andreas Heckel

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='007801c63323$77c6b160$a501a8c0@CAM.ARTIMI.COM' \
    --to=dave.korn@artimi.com \
    --cc=cygwin@cygwin.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).