Discover MakerZone

MATLAB and Simulink resources for Arduino, LEGO, and Raspberry Pi

Learn more

Discover what MATLAB® can do for your career.

Opportunities for recent engineering grads.

Apply Today

Thread Subject:
Constrained Delaunay triangulation

Subject: Constrained Delaunay triangulation

From: hpc

Date: 30 Mar, 2010 12:03:23

Message: 1 of 4

I am doing Constrained Delaunay triangulation and matlab crashes while
doing so

I do

dt=DelaunayTri(mesh_xy, C)

where mesh_xy holds the information of the coordinates of the mesh
where this mesh has to be created and C has the value of the
coordinates of the edges.
this command crashes and tells me to exit matlab and restart.
have a look at the details


MATLAB crash file:/home-link/zxmvx31/matlab_crash_dump.12245
------------------------------------------------------------------------
       Segmentation violation detected at Tue Mar 30 14:02:20 2010
------------------------------------------------------------------------

Configuration:
  MATLAB Version: 7.8.0.347 (R2009a)
  MATLAB License: 556154
  Operating System: Linux 2.6.18-164.11.1.el5 #1 SMP Wed Jan 20
00:57:09 EST 2010 x86_64
  GNU C Library: 2.5 stable
  Window System: The X.Org Foundation (10400090), display localhost:
10.0
  Current Visual: 0x21 (class 4, depth 24)
  Processor ID: x86 Family 6 Model 10 Stepping 5, GenuineIntel
  Virtual Machine: Java 1.6.0_04-b12 with Sun Microsystems Inc. Java
HotSpot(TM) 64-Bit Server VM mixed mode
  Default Encoding: UTF-8

Fault Count: 1

Register State:
  rax = 0000000000000000 rbx = 00000000060cc1a0
  rcx = 0000000000000002 rdx = 0000000000000002
  rbp = 000000007ff64740 rsi = 000000007ff647e0
  rdi = 00002aab28b9be40 rsp = 000000007ff64740
   r8 = 00002aabcebde06c r9 = 00002aab292708f0
  r10 = 0000000000000001 r11 = 0000000000000002
  r12 = 0000000000000000 r13 = 0000000000000002
  r14 = 0000000006729610 r15 = 00002aab28b9be40
  rip = 00002aabceb6975a flg = 0000000000010246

Stack Trace:
  [0] libmwmathcgeo.so:0x00002aabceb6975a(16, 0, 0x2aab283e2850,
0x7ff647d0)
  [1] libmwmathcgeo.so:0x00002aabceb7d52e(0x2aab28b9bf48 ", 0x7ff64af0
", 0x7ff64b50 ", 0x7ff64b60 ")
  [2] libmwmathcgeo.so:0x00002aabceb5f07c(0x7ff64d50 ", 0x7ff64d60,
0x7ff64d70 ", 0x7ff64d80)
  [3] libmwmathcgeo.so:0x00002aabceb5f740(0x2aabc43e45f0,
0x2aab28b9bd90, 0x7ff64ec0, 0x2aabcebb5c88)
  [4] libmwmathcgeo.so:0x00002aabcebc7b04(0x2af8fa199e40,
0x2aabc43e4728, 0x2aabc43e46c0, 0x2af8f51e8ea5)
  [5] libmwmathcgeo.so:0x00002aabcebb5c88(0x7ff64fd0, 0x2aab28b9bdd0
"XF>ī*", 0x2aab292a2830 ", 0x2aab29368fe0 ")
  [6] libmwmcos.so:MethodDispatcher::callConstructor()(0x2aab00000002,
0x7ff65840 ", 0, 0x2aab00000000) + 434 bytes
  [7] libmwmcos.so:omCallConstructor(mcos::COSClassI*, mcos::COSClient
const*, int, mxArray_tag const**)(0x2aab28bd1270 ", 0x2af8fa0a46d2,
0x2aab28e14570, 0x2aab28b9bd00 ") + 162 bytes
  [8] libmwmcos.so:omCallTopLevelConstructor(mcos::COSClassI*,
mcos::COSClient const*, int, mxArray_tag const**)(0x7ff65300,
0x7ff65220, 0x7ff65330, 0x7ff65280 ") + 29 bytes
  [9] libmwmcos.so:omConstructObjectWithClient(mxArray_tag*, int,
mxArray_tag const**, mcos::COSClient const*)(0x2af8f6347cf0,
0x05045da0, 0x7ff65780, 0x2aab295ec810 ") + 630 bytes
  [10] libmwmcos.so:Mfh_opaque_constructor::dispatch_mf(int,
mxArray_tag**, int, mxArray_tag**)(0x7ff65840 ", 0x2292a28a0,
0x2aab295ec810 ", 0x7ff66ab0) + 149 bytes
  [11] libmwm_dispatcher.so:Mfh_MATLAB_fn::dispatch_fh(int,
mxArray_tag**, int, mxArray_tag**)(0x17ff65490, 0x2af8ffffffff,
0x2aab284b6b60, 0) + 234 bytes
  [12] libmwm_interpreter.so:ResolverFunctionDesc::CallFunction(int,
mxArray_tag**, int, mxArray_tag**)(2593, 0x100000000, 0x7ff66320,
0x3fe04005) + 871 bytes
  [13] libmwm_interpreter.so:Resolver::CallMFunction(int, int,
_m_operand*, m_operand_storage*, int, _m_operand*, m_operand_storage*,
int*)(0x2aab295abd10, 0, 0x7ff664f0, 0) + 1637 bytes
  [14] libmwm_interpreter.so:inResolveMFunctionCall(_m_function_desc*,
int, int, _m_operand*, m_operand_storage*, int, _m_operand*,
m_operand_storage*, int*, inMarshalType*, int, mpsTypeSequenceNlhs
const*, mxArray_tag* (*)(int))(0x2aab295abd10, 0, 0x7ff664f0,
0x7ff66698) + 501 bytes
  [15] libmwm_interpreter.so:accelImpl::MFunctionCall(_accelOp**)
(0x7ff66484, 0x2aab2932dbd0, 0x17ff664e0, 0x2aab28e33590) + 239 bytes
  [16] libmwm_interpreter.so:accelImpl::Exec()(0x7ff66698, 0x7ff66690,
0x2aab28dedf80, 0x2aab28e10320 ") + 273 bytes
  [17] libmwm_interpreter.so:accelCode::Call(inMarshalType*, int*)
const(0x7ff66698, 0x7ff66690, 0x7ff66640, 0x7ff6669f) + 91 bytes
  [18]
libmwm_interpreter.so:inJit::ExecuteHotSegment(_inJitAccelInfo*,
opcodes*, int*, long*)(0x7ff66710, 0x7ff6675c, 0xffffffff0000006f,
0xffffffff00000000) + 1793 bytes
  [19] libmwm_interpreter.so:inExecuteMFunctionOrScript(Mfh_mp*, bool)
(0x7ff66810, 0x7ff669f0, 0, 0) + 1104 bytes
  [20] libmwm_interpreter.so:inRunMfile(int, mxArray_tag**, int,
mxArray_tag**, Mfh_mp*, inWorkSpace_tag*)(0, 0x28000020,
0x2aab28df1040, 0x7ff67ad0) + 1411 bytes
  [21] libmwm_dispatcher.so:Mfh_file::dispatch_fh(int, mxArray_tag**,
int, mxArray_tag**)(0x7ff66b50, 0, 0x7ff67870, 0x7ff676c0) + 282 bytes
  [22] libmwm_interpreter.so:inEvalPcodeHeaderToWord(_memory_context*,
int, mxArray_tag**, _pcodeheader*, Mfh_mp*, unsigned int)(0x7ff66b70,
0x7ff66d40, 0x7ff678c0, 0) + 170 bytes
  [23]
libmwm_interpreter.so:in_local_call_script_function(_memory_context*,
_pcodeheader*, int, mxArray_tag**, unsigned int, bool)(0x7ff66c00,
0x2aaba9666df7, 0x7ff677c8 ", 0x7ff677d4) + 103 bytes
  [24]
libmwm_interpreter.so:inEvalStringWithIsVarFcn(_memory_context*, char
const*, EvalType, int, mxArray_tag**, inDebugCheck, _pcodeheader*,
int*, bool (*)(void*, char const*), void*, bool, bool)(0, 0,
0x2af8f6425fc0, 0) + 2610 bytes
  [25] libmwm_interpreter.so:inEvalCmdWithLocalReturn(char const*,
int*, bool, bool, bool (*)(void*, char const*))(0x7ff678d0,
0x2aab295bc490 "dt=DelaunayTri(mesh_xy, boundary..", 0x7ff67a90, 0) +
149 bytes
  [26] libmwbridge.so:evalCommandWithLongjmpSafety(char const*)
(0x7ff67aa0, 0x7ff67af0, 0x7ff67b00 ", 0x7ff67b10) + 94 bytes
  [27] libmwbridge.so:mnParser(0x04a97680, 0x2aab28ba6e30, 0x06466f01,
55) + 355 bytes
  [28] libmwmcr.so:mcrInstance::mnParser_on_interpreter_thread()(0,
0x04c30590, 0x04c30590, 0x04c30590) + 41 bytes
  [29] libmwmcr.so:boost::function0<void>::operator()()
const(0x100000004, 0x7ff67c80, 0x7ff67c40, 0x2af8f5e96e71) + 123 bytes
  [30]
libmwmcr.so:mcr::runtime::InterpreterThread::Impl::NoResultInvocationRequest::run()
(0x7ff67c80, 0x2aab28c64ae0, 0x2aab295b0080, 0x2aab28c64ae0) + 21
bytes
  [31]
libmwmcr.so:mcr::runtime::InterpreterThread::Impl::invocation_request_handler(long)
(0x7ff67c80, 0x7ff67d40, 0x7ff67aa0, 0x3000000020) + 33 bytes
  [32] libmwuix.so:uix_DispatchOrProcess(_XEvent*, _XtAppStruct*, int,
bool)(0x04a9c4e0, 0x2af8f4a2cb5c, 0x7ff67e90, 0x1002af800000001) + 361
bytes
  [33] libmwuix.so:ws_ProcessPendingEventsHelper(int, int, bool)(9,
0x04a96220, 0x04a9b970 ", 0x04a9b8d0) + 489 bytes
  [34]
libmwmcr.so:mcr::runtime::InterpreterThread::Impl::process_events(boost::shared_ptr<mcr::runtime::InterpreterThread::Impl>
const&)(0x04a96238, 0x7ff67f90, 0x0504d300, 0x3034a0cd00) + 225 bytes
  [35]
libmwmcr.so:mcr::runtime::InterpreterThread::Impl::run(boost::shared_ptr<mcr::runtime::InterpreterThread::Impl>
const&, mcr::runtime::InterpreterThread::Impl::init_context*)
(0x04a9b8d0, 0x04a9b970 ", 0x04a973b0, 0x7ff68080 ") + 237 bytes
  [36] libmwmcr.so:run_init_and_handle_events(void*)(0x2aaae92ab9d0 ",
0x2af8f4a2cb5c, 0, 0x00402670) + 60 bytes
  [37] MATLAB:boost::function0<void>::operator()()
const(0x7fffa9511c88, 0x1069cb120, 0, 0x04a973b0) + 412 bytes
  [38] MATLAB:mcrMain(int, char const**)(0x7ff681c0, 0x7ff68940, 0, 0)
+ 243 bytes
  [39] libmwmcr.so:runMcrMain(void*)(0, 0x7ff68940, 0, 0) + 28 bytes

Please follow these steps to report this problem to The MathWorks so
we
have the best chance of correcting it:

The next time MATLAB is launched under typical usage, a dialog box
will
open to help you send the error log to The MathWorks. Alternatively,
you
can send an e-mail to segv@mathworks.com with the following file
attached:
    /home-link/zxmvx31/matlab_crash_dump.12245

If the problem is reproducible, please submit a Service Request via:
    http://www.mathworks.com/support/contact_us/ts/help_request_1.html

A technical support engineer might contact you with further
information.

Thank you for your help. MATLAB may attempt to recover, but even if
recovery appears successful,
we recommend that you save your workspace and restart MATLAB as soon
as possible.

Subject: Constrained Delaunay triangulation

From: Steven Lord

Date: 30 Mar, 2010 13:35:52

Message: 2 of 4


"hpc" <ashutoshsingh.ashu@gmail.com> wrote in message
news:1aa84687-459f-4567-9ee7-a14fd4340dcb@o30g2000yqb.googlegroups.com...
> I am doing Constrained Delaunay triangulation and matlab crashes while
> doing so
>
> I do
>
> dt=DelaunayTri(mesh_xy, C)
>
> where mesh_xy holds the information of the coordinates of the mesh
> where this mesh has to be created and C has the value of the
> coordinates of the edges.
> this command crashes and tells me to exit matlab and restart.
> have a look at the details

Please send a MAT-file containing the variables mesh_xy and C along with the
crash log file you included in your post to Technical Support so that we can
investigate the cause of this behavior. You can contact Technical Support
via the Contact Us link at the top of http://www.mathworks.com. Thanks.

--
Steve Lord
slord@mathworks.com
comp.soft-sys.matlab (CSSM) FAQ: http://matlabwiki.mathworks.com/MATLAB_FAQ

Subject: Constrained Delaunay triangulation

From: Dave Brackett

Date: 24 Feb, 2012 15:27:21

Message: 3 of 4

"Steven Lord" <slord@mathworks.com> wrote in message <hosun5$3as$1@fred.mathworks.com>...
>
> "hpc" <ashutoshsingh.ashu@gmail.com> wrote in message
> news:1aa84687-459f-4567-9ee7-a14fd4340dcb@o30g2000yqb.googlegroups.com...
> > I am doing Constrained Delaunay triangulation and matlab crashes while
> > doing so
> >
> > I do
> >
> > dt=DelaunayTri(mesh_xy, C)
> >
> > where mesh_xy holds the information of the coordinates of the mesh
> > where this mesh has to be created and C has the value of the
> > coordinates of the edges.
> > this command crashes and tells me to exit matlab and restart.
> > have a look at the details
>
> Please send a MAT-file containing the variables mesh_xy and C along with the
> crash log file you included in your post to Technical Support so that we can
> investigate the cause of this behavior. You can contact Technical Support
> via the Contact Us link at the top of http://www.mathworks.com. Thanks.
>
> --
> Steve Lord
> slord@mathworks.com
> comp.soft-sys.matlab (CSSM) FAQ: http://matlabwiki.mathworks.com/MATLAB_FAQ
>

I am also finding that MATLAB crashes on me when using constrained delaunay. I don't get any error message but a complete closure of MATLAB (on two different computers). Did this get looked at any further? I'm using v2010b.

Subject: Constrained Delaunay triangulation

From: Steven_Lord

Date: 27 Feb, 2012 15:30:19

Message: 4 of 4



"Dave Brackett" <davebrackett@hotmail.com> wrote in message
news:ji8a8p$e9c$1@newscl01ah.mathworks.com...
> "Steven Lord" <slord@mathworks.com> wrote in message
> <hosun5$3as$1@fred.mathworks.com>...

*snip*

> I am also finding that MATLAB crashes on me when using constrained
> delaunay. I don't get any error message but a complete closure of MATLAB
> (on two different computers). Did this get looked at any further? I'm
> using v2010b.

Please send the data that causes MATLAB to crash when you pass it into
DelaunayTri (and the exact code you're using to create the DelaunayTri
object) to Technical Support for further investigation. They can work with
the development staff to determine if you're experiencing the same problem
as hpc or a different one.

--
Steve Lord
slord@mathworks.com
To contact Technical Support use the Contact Us link on
http://www.mathworks.com

Tags for this Thread

No tags are associated with this thread.

What are tags?

A tag is like a keyword or category label associated with each thread. Tags make it easier for you to find threads of interest.

Anyone can tag a thread. Tags are public and visible to everyone.

Contact us