Re: [gccsdk] stderr 2 file advantage

In message <5b44d00053.beeb@ron1954.woosh.co.nz>
Ron <beeb@woosh.co.nz> wrote:

> In message <6cddca0053.Jo@hobbes.bass-software.com>
> John Tytgat <John.Tytgat@aaug.net> wrote:
>
> > In message <f2d8c70053.beeb@ron1954.woosh.co.nz>
> > Ron <beeb@woosh.co.nz> wrote:
> >
> > > I'm not using the very latest crosscompiler, but I think this will be
> > > unchanged.
> > > Using my port of tar
> > >
> > > tar -xvf ztmp.tar
> > >
> > > stops with "UnixLib detected recursion of signal SIGSEGV. Exiting."
> > > when I encounter a pax format tar, (unless I specify --format=pax)
> > >
> > > I set about trapping the error (in an obey file way) by using
> > >
> > > tar -xvf ztmp.tar 2> errlog
> > >
> > > so I could check a file for an error.
> > >
> > > But when I do this, the program /does/ create the file errlog,
> > > but it remains empty, and tar now continues on and extracts the
> > > pax format tar perfectly as if --format=pax has been used!
> > >
> > > A good result, but it raises the question why, and does stderr
> > > always need to be directed somewhere for better behaviour?
> >
> > Are you launching tar straight from CLI ? Or is this in a fork()/exec()
> > /system() done ?
>
> Either from an Obey file or from the CLI in a taskwindow, same result.
> From memory,fork() is only used for the multipart tar activity.
>
> Directing stderr to stdout works equally as well.
>
> tar -xvf ztmp.tar 2>&1

Very bizar, looks like a real bug somewhere but someone needs to dig into
this as I don't think we can just guess it based on above facts only.

John.
--
John Tytgat, in his comfy chair at home
John.Tytgat@aaug.net

_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK