[M3devel] full paths to sources to slightly ease debugging self-built binaries?

[Olaf Wagner]

Quoting Jay <jayk123 at hotmail.com>:

>  >> And I think we should fix it so that that the symbols have full   
> source paths. >> I realize they would only be correct on one   
> machine, and hopefully there's a decent story for copying the files.
>
> My experience using gdb suggests that the symbols have paths like   
> foo.m3 and/or ../bar.i3 but never "full paths".
> You can tell gdb where to look for files, it isn't that hard, and it works.

What exactly is the full path of a module? That of your private
workspace (assuming you are using overrides for everything) or
that in the global package pool (/usr/local/cm3/pkg/...)?

Olaf
-- 
Olaf Wagner -- elego Software Solutions GmbH
                Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
phone: +49 30 23 45 86 96  mobile: +49 177 2345 869  fax: +49 30 23 45 86 95
    http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194