http://www.mapleprimes.com/questions/139362-1st-Vector-Dimension-Size-Is-Too-Small en-us 2026 Maplesoft, A Division of Waterloo Maple Inc. Maplesoft Document System Sat, 13 Jun 2026 20:40:25 GMT Sat, 13 Jun 2026 20:40:25 GMT The latest answers and comments added to the Question, 1st Vector dimension size is too small to fit source size http://www.mapleprimes.com/images/mapleprimeswhite.jpg http://www.mapleprimes.com/questions/139362-1st-Vector-Dimension-Size-Is-Too-Small http://www.mapleprimes.com/questions/139362-1st-Vector-Dimension-Size-Is-Too-Small?ref=Feed:MaplePrimes:1st Vector dimension size is too small to fit source size:Comments#answer139376 <p>A simple way is to use the <a href="http://www.maplesoft.com/support/help/search.aspx?term=trace">?trace</a> command.&nbsp; Execute</p> <pre>trace(myproc):</pre> <p>where myproc is the name of your procedure, then execute your procedure.&nbsp; The output of each statement is printed.&nbsp; From that you might be able to figure out where the error occurs.</p> <p>Better is to use the debugger.&nbsp; Execute the command</p> <pre>stoperror('all'):</pre> <p>That tells Maple to launch the debugger when an untrapped error occurs. Execute your procedure.&nbsp; That should cause the debugger to be launched with the control at the place in the procedure that raises the error. That will likely be inside a Maple library procedure called by your procedure. To figure out the cause you can query the values of variables and expressions in the procedure.</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>A simple way is to use the <a href="http://www.maplesoft.com/support/help/search.aspx?term=trace">?trace</a> command.&nbsp; Execute</p> <pre>trace(myproc):</pre> <p>where myproc is the name of your procedure, then execute your procedure.&nbsp; The output of each statement is printed.&nbsp; From that you might be able to figure out where the error occurs.</p> <p>Better is to use the debugger.&nbsp; Execute the command</p> <pre>stoperror('all'):</pre> <p>That tells Maple to launch the debugger when an untrapped error occurs. Execute your procedure.&nbsp; That should cause the debugger to be launched with the control at the place in the procedure that raises the error. That will likely be inside a Maple library procedure called by your procedure. To figure out the cause you can query the values of variables and expressions in the procedure.</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> <p>&nbsp;</p> 139376 Fri, 09 Nov 2012 10:20:43 Z Joe Riel Joe Riel