Attempted to access error by using the profiler

The matlab profile function displays an "attempted to access error" during a regular usage (R2009b).
??? Attempted to access o.lnos(340); index out of bounds because numel(o.lnos)=339.
Error in ==> mtree.mtree>mtree.lastone at 1794 ch = Pos - o.lnos(ln);
Error in ==> getcallinfo at 92 functionInfo.lastline = lastone(last(rootNode));
Error in ==> profview>makefilepage at 1104 strc = getcallinfo(fullName,'-v7.8');
Error in ==> profview at 71 s = makefilepage(profileInfo,idx, busyLineSortKeyStr2Num(busyLineSortKey));
Does anybody know how avoid this error?

2 commentaires

Jan
Jan le 20 Nov 2012
Modifié(e) : Jan le 20 Nov 2012
Yes, Jose-Luis: the question is, if anybody knows how to avoid this error.
José-Luis
José-Luis le 20 Nov 2012
Sorry about the previous (now deleted) comment, I had misunderstood the question.

Connectez-vous pour commenter.

 Réponse acceptée

Jan
Jan le 20 Nov 2012
Modifié(e) : Jan le 20 Nov 2012

0 votes

I've seen this error, when I had edited an M-file during processing. Such things will confuse the profiler tremendously. It could be a problem also, when you run P-code, while the profiler tries to display the corresponding line of the M-file, but both files are different.
What do you find in the lines 339 and 340 of the concerned M-file?

Plus de réponses (1)

Daniel
Daniel le 20 Nov 2012
Modifié(e) : Daniel le 20 Nov 2012

0 votes

Thanks Simon but I did not edit anything during during processing. I used the profiler to check an easy M-file with 332 lines. Nothing special. Even if I restart the system I'll get this error.

Catégories

Tags

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by