[Octave-bug-tracker] [bug #49642] Traceback from errors in private functions is incomplete

[Philip Nienhuis]

URL:
  <http://savannah.gnu.org/bugs/?49642>

                 Summary: Traceback from errors in private functions is
incomplete
                 Project: GNU Octave
            Submitted by: philipnienhuis
            Submitted on: Fri 18 Nov 2016 10:10:25 AM CET
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: Philip Nienhuis
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

Revisiting big #49635, an issue that hindered effective tracking down here the
bug occurred was that the error traceback was incomplete (stanza for
convenience repeated from bug report 49635):

:
make: Leaving directory `/tmp/oct-qVNFk3/octclip-1.0.8/src'
copyfile
C:\Users\philip\AppData\Local\Temp\oct-qVNFk3\octclip-1.0.8\src\_oc_polyboo
l.oct
C:\Users\philip\AppData\Local\Temp\oct-qVNFk3\octclip-1.0.8\inst\x86_64-w64-mi
ngw32-api-v51
'desc' undefined near line 30 column 43
error: called from
    install at line 242 column 5
    pkg at line 394 column 9



while the actual error occurred in
./pkg/private/default_prefix.m   (not mentioned, but correct line number in
traceback)
called from:
./pkg/private/install.m >subfunction> create_pkgadddel  (not mentioned)
called from:
./pkg/private/install.m  (mentioned fine, "correct"[*] line no.).

Maybe this is due to default_prefix being called from a subfunction of another
private function?

[*]
Another issue is that the line number in install.m is "correct" in the sense
that it is the line number where 
"rethrow (lasterror())"
is called. But the actual error occurred in a function call on L.228.  IOW,
this is a bit deceiving.
Is there a way to uncover the actual line number where an error occurred when
calling rethrow?





    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?49642>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/