From: abaghda Baghdasaryan on 19 Apr 2010 04:00 Hello, my name is Anna. Currently I am working on my IT project where I use matlab. I have a problem when trying to run the ready code on other computer. It is a GUI program created with guide which works fine on my computer, but when I try to run it on other computer it displays ''Segmentation violation detected at... '' long message. It happens quite often, so I really need to find a solution to this problem. Please help me with this issue. Thanks
From: Rune Allnor on 19 Apr 2010 04:52 On 19 apr, 10:00, "abaghda Baghdasaryan" <spika8...(a)yahoo.com> wrote: > Hello, > my name is Anna. Currently I am working on my IT project where I use matlab. I have a problem when trying to run the ready code on other computer.. It is a GUI program created with guide which works fine on my computer, but when I try to run it on other computer it displays ''Segmentation violation detected at... '' long message. It happens quite often, so I really need to find a solution to this problem. Please help me with this issue. This is almost certainly caused by a MEX file somewhere in your system. Track down what MEX file this is (i.e. read that error message) and talk with the author of the MEX file. Rune
From: Nitin on 20 Apr 2010 02:25 This is what you are probably looking for: http://www.mathworks.com/support/solutions/en/data/1-663J0X/index.html?product=ML Rune Allnor <allnor(a)tele.ntnu.no> wrote in message <14e0ec01-12c1-4445-ae2c-11c7d542e540(a)q23g2000yqd.googlegroups.com>... > On 19 apr, 10:00, "abaghda Baghdasaryan" <spika8...(a)yahoo.com> wrote: > > Hello, > > my name is Anna. Currently I am working on my IT project where I use matlab. I have a problem when trying to run the ready code on other computer. It is a GUI program created with guide which works fine on my computer, but when I try to run it on other computer it displays ''Segmentation violation detected at... '' long message. It happens quite often, so I really need to find a solution to this problem. Please help me with this issue. > > This is almost certainly caused by a MEX file somewhere in your > system. > Track down what MEX file this is (i.e. read that error message) and > talk with the author of the MEX file. > > Rune
|
Pages: 1 Prev: discharge prediction, ar-model Next: connected component algorithm with given predicate |