Pathnames followed by "..." when printed using printpathn

[Dmitry V. Levin]

On Wed, May 28, 2014 at 05:53:16PM +0200, Philippe Ombredanne wrote:
> On Wed, May 28, 2014 at 4:42 PM, Zubin Mithra <zubin.mithra at gmail.com> wrote:
> > I've added in the code for converting all paths that are printed via
> > printpathn(hence, all paths via printpath too). Please find the code at [1].
> > The sample output can be found here[2].
> > [1]
> > https://github.com/eQu1NoX/strace/commit/b17aa1a8a20a8171ad1266fa13ffd492f3e23d3f
> > [2] https://gist.github.com/eQu1NoX/35e66c569c4a3f06cfd3
> 
> I see you are printing only the relative path if you failed to get a
> real path for some reason.
> I wonder if there could be something that could hint the reader that
> absolute path resolution failed?

Every relative path in the output where only absolute paths are expected
is a clear hint that absolute path resolution failed. :)


-- 
ldv
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.strace.io/pipermail/strace-devel/attachments/20140528/638c6b47/attachment.bin>