From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: headache on build repeatibility: octave vs BLODA ?
Date: Mon, 27 Jan 2020 06:45:00 -0000 [thread overview]
Message-ID: <0fb5712c-7d57-d5cb-56b7-3a0d2f44d8a2@gmail.com> (raw)
In-Reply-To: <08ac898e-e7f9-c8e9-91ba-d4ee33f2e27c@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1864 bytes --]
Am 26.01.2020 um 09:38 schrieb Marco Atzeri:
> Am 26.01.2020 um 09:05 schrieb ASSI:
>> Marco Atzeri writes:
>>> at least I know that is not just my machine.
>>> When I released the package was
>>>
>>>
>>> Â Â libinterp/corefcn/file-io.cc-tst
>>> ............................... PASS 90/90
>>
>> Based on the test name there may be an assumption built into the code
>> about how the filesystem behaves that isn't guaranteed on Windows/Cygwin
>> or even POSIX. If it's simply an error condition not getting checked it
>> should be reproducible under debugging, but you're mostly out of luck if
>> it's relying on a specific order or atomicity of certain operations, as
>> debugging will almost always serialize the execution to the point where
>> these types of errors do not manifest.
>>
>>
>> Regards,
>> Achim.
>
> the other problem of debugging is that the backtrace is trash
> after the segfault and that of course Octave is a
> 400 Kg gorilla with all its dependencies..
>
> I will try anyway
>
> Thanks
> Marco
>
one thing that I noticed is that the old binary I released and
the new one built are behaving differently.
So whatever is the problem that you and me are seeing and that
Takashi's system seems immune is causing a difference at
compilation time in the executable:
Old binary:
octave:2> run test-round6a.m
octave:3> run test-round6b.m
New binary:
octave:1> run test-round6a.m
fatal: caught signal Segmentation fault -- stopping myself...
Segmentation fault (core dumped)
octave:1> run test-round6b.m
fatal: caught signal Segmentation fault -- stopping myself...
Segmentation fault (core dumped)
Can you and Takashi provide me your cygcheck.out so that I can look on
possible difference that could influence the build behaviour.
Of course I have W10 Home and Takashi a W10 Pro an that is already
a difference.
Regards
Marco
[-- Attachment #2: test-round6a.m --]
[-- Type: text/plain, Size: 206 bytes --]
f = tempname ();
fid = fopen (f, "w+");
fprintf (fid, "1\n2\n3\n4\n5\n6");
fseek (fid, 0, "bof");
c = textscan (fid, "%f %f", 2);
E = feof (fid);
fclose (fid);
unlink (f);
assert (c, {1, 2});
assert (! E);
[-- Attachment #3: test-round6b.m --]
[-- Type: text/plain, Size: 188 bytes --]
f = tempname ();
fid = fopen (f, "w+");
fprintf (fid, "1\r\n2\r3\n4\r\n5\n6");
fseek (fid, 0, "bof");
c = textscan (fid, "%f %f", 4);
fclose (fid);
unlink (f);
assert (c, {[1;3], [2;4]});
[-- Attachment #4: Type: text/plain, Size: 219 bytes --]
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2020-01-27 6:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 16:55 Marco Atzeri
2020-01-25 18:15 ` Brian Inglis
2020-01-27 6:54 ` Marco Atzeri
2020-01-25 20:36 ` Achim Gratz
2020-01-26 6:58 ` Marco Atzeri
2020-01-26 8:05 ` ASSI
2020-01-26 8:38 ` Marco Atzeri
2020-01-27 6:45 ` Marco Atzeri [this message]
2020-01-27 11:33 ` Takashi Yano
2020-01-28 6:41 ` Marco Atzeri
2020-01-28 14:55 ` Takashi Yano
2020-01-29 9:44 ` Corinna Vinschen
2020-01-29 12:19 ` Marco Atzeri
2020-01-29 13:46 ` Takashi Yano
2020-01-29 15:11 ` Takashi Yano
2020-01-29 15:32 ` Corinna Vinschen
2020-01-29 15:34 ` Corinna Vinschen
2020-01-29 16:08 ` Takashi Yano
2020-01-29 17:57 ` Corinna Vinschen
2020-01-30 21:05 ` Brian Inglis
2020-01-30 21:34 ` Marco Atzeri
2020-01-28 17:26 ` ASSI
2020-01-28 20:04 ` Marco Atzeri
2020-01-28 20:21 ` Achim Gratz
2020-01-26 2:42 ` Takashi Yano
2020-01-26 5:11 ` Takashi Yano
2020-01-26 10:24 ` Marco Atzeri
2020-01-26 10:31 ` Takashi Yano
2020-01-29 0:03 ` Hans-Bernhard Bröker
2020-01-29 0:39 ` Hans-Bernhard Bröker
2020-01-29 5:10 ` Marco Atzeri
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=0fb5712c-7d57-d5cb-56b7-3a0d2f44d8a2@gmail.com \
--to=marco.atzeri@gmail.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).