RE: using make to run binaries

[Dave Korn]

On 18 September 2007 08:26, Andreas Maunz wrote:

>  > The situation smells like undefined behaviour to me; if you're using
>  > an uninitialised variable or in some other way depending on random
>  > memory contents, that could trigger the different behaviour in your
>  > program. Your description of the problem is a bit vague, but by
>  > "more chemical information", I'm guessing the library is either
>  > returning more records, or more data fields in each record.
> 
> The output consists mainly of chemical compounds. Every compound has a
> score attached (a floating point number). When run with make, lower
> scores are attached and thus more chunks fall below a predefined
> threshold (0.3) which results in less output. The score is a measure of
> similarity between the compounds and one specific compound, called the
> query compound. For similarity computation the already mentioned
> libraries are accessed. It really seems that is has something to do with
> program internal computation and/or the way libraries are accessed.
> 
> The manual results seem to make much more sense, so in the meantime I
> have decided to refer to them as "correct".

  Here's a thought: does it still happen if you compile your program with -O0,
i.e. no optimisation?  


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