I test this snapshot and the different problems linked to the thread
under disappeared
http://cygwin.com/ml/cygwin-xfree/2004-11/msg00192.html
Thanks for your work
B.Patin
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Do
Brian Ford a écrit :
You're calling a cygwin DLL (not -mno-cygwin) from matlab? I don't think
this will work in the general sense. You may have been lucky before.
In order to do that I use a tool developped by M.Brett and that do the
job of connecting the cygwin dll to matlab. Excuse me not t
Brian Ford a écrit :
On Sun, 9 May 2004, bruno patin wrote:
There you're right. What I'm afraid of is that the cygwin code is not
called at all and as it is matlab that calls it I'll be unable to do
that debugging (we'll see). If I arrive to some results I'll let the
Hi,
I've already sent a mail on this topic (see the joined mail). I can't
say I advance a lot. So my new question. I'm now trying to see what can
happen inside matlab during the crash. I tried strace but nothing
occured. I even try purify but for the time being it is a failure. Do
you know a to
Stating anything here would be pure speculation. There are obviously some
differences among these platforms, though generally of little consequence
to Cygwin. However, even on exactly the same hardware, there are sometimes
differences that can have an affect. But the only way to track down you
Hi all,
I know it's perhaps not the good list but I'm searching information on
what could happen on a cygwin generated mexfile for matlab under xp.
The facts :
With the gnumex tool I created lots of cygwin dll (called mexfiles under
matlab) and, under NT, I use them without any pbs. good stabi
6 matches
Mail list logo
