caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Florent Monnier <monnier.florent@gmail.com>
To: Adrien Nader <adrien@notk.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: portable truncate
Date: Sat, 27 Jul 2013 21:45:18 +0200	[thread overview]
Message-ID: <CAE1DttAa6aNKGt=586gBt-prcFhQLezPthNCE25h0bY_dcL8Tw@mail.gmail.com> (raw)
In-Reply-To: <20130727154347.GA3385@notk.org>

2013/7/27, Adrien Nader wrote:
> On Sat, Jul 27, 2013, Florent Monnier wrote:
[...]
>> mingw's additional lib has to be used if we're using thread for
>> example if I have understood correctly.
>
> What makes you think so?

The sentence below that is on the website of the project:

"It does depend on a number of DLLs provided by Microsoft themselves,
as components of the operating system; most notable among these is
MSVCRT.DLL, the Microsoft C runtime library. Additionally, threaded
applications must ship with a freely distributable thread support DLL,
provided as part of MinGW itself"

> A quick look seems to indicate the opposite. There is no specific thread
> support provided by mingw*.
> There are pthreads-win32 and winpthreads but I don't see the build
> system use them on Windows; I see calls to CreateThead() (typical win32
> stuff) however for instance.
>
>> >> - truncate()  DOES work on my computer
>> >> - ftruncate() / _chsize()  DOESN'T
>> >
>> > That's surprising and you should really try to see which error you get
>> > throw errno. You can also try a tool like FileMonitor (or whatever it's
>> > called nowadays) to see how it fails.
>>
>> I get EBADF
>>
>> http://msdn.microsoft.com/en-us/library/dk925tyb%28v=VS.80%29.aspx
>>
>> EBADF is if the specified file is read-only or the descriptor is invalid
>>
>> the file has write access for everyone.
>> And the file descriptor is converted the same way than everywhere else.
>>
>> Then I noticed that I copied the stub from otherlibs/unix/ not from
>> otherlibs/win32unix/
>> so the file descr is converted by Int_val() instead of Handle_val().
>>
>> But now I still get : EBADF
>
> And you've opened the file as read-write too?

let open_flags = [Unix.O_RDWR]
O_RDWR  (* Open for reading and writing *)


> If so, you should maybe try Process Monitor to make sure everything was
> done as expected:
>   http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

Thanks Adrien, I'll have a look at this tomorrow.

-- 
Regards

  reply	other threads:[~2013-07-27 19:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26 10:35 [Caml-list] " Florent Monnier
2013-07-26 10:46 ` Mihamina Rakotomandimby
2013-07-26 10:48   ` Török Edwin
2013-07-26 10:52 ` Daniel Bünzli
2013-07-26 12:02 ` [Caml-list] " Florent Monnier
2013-07-27  7:05   ` David Allsopp
2013-07-27  8:54     ` Florent Monnier
2013-07-27  8:38   ` Adrien Nader
2013-07-27  9:05     ` Adrien Nader
2013-07-27 14:11     ` Florent Monnier
2013-07-27 14:23       ` Adrien Nader
2013-07-27 15:34         ` Florent Monnier
2013-07-27 15:43           ` Adrien Nader
2013-07-27 19:45             ` Florent Monnier [this message]
2013-07-27 19:53               ` Adrien Nader
2013-07-27 20:03                 ` Török Edwin
     [not found] ` <20130727181711.65d8456f@kiwi.local.tld>
2013-07-27 14:41   ` [Caml-list] " Florent Monnier
2013-07-27 15:26     ` Adrien Nader
2013-07-27 15:40       ` Florent Monnier

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='CAE1DttAa6aNKGt=586gBt-prcFhQLezPthNCE25h0bY_dcL8Tw@mail.gmail.com' \
    --to=monnier.florent@gmail.com \
    --cc=adrien@notk.org \
    --cc=caml-list@inria.fr \
    /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 NNTP newsgroup(s).