Re: unusable backtrace

[Werner LEMBERG]

>> * The compilation output says, for example,
>>
>>   ```
>>   ;;; compiling 
>> /home/wl/lilypond/out/share/lilypond/current/scm/lily/graphviz.scm
>>   ;;; compiled 
>> /home/wl/lilypond/out/share/lilypond/current/guile/ccache/2.2-LE-8-3.A/home/wl/lilypond/scm/graphviz.scm.go
>>   ```
>>
>>   This is strange: What does '2.2-LE-8-3.A' mean?
> 
> 2.2 would likely be the major version, LE little endian, 8 could be
> the cell size and, well, whatever.  Basically the path encodes the
> details of the bytecode architecture, and then the source path.

Thanks.  While this sounds useful, ...

>>   Why do I get two paths concatenated?
> 
> Because the first path indicates the architecture and involved
> executable, and the second path indicates the source path of the
> compiled file.

... it is a complete madness to *concatenate* these details into a
crazy, long string that resembles a path but shows wrong directories.
I'm sure there is a bug somewhere (or I'm doing something wrong).


    Werner