Re: [geomview-users] SaVi segfaulting when writing to a geomview pipe?

[<llo...@ya...>]

Thanks for the suggestion.

I'm pretty familiar with and involved in the packaging of SaVi on ubuntu
and on cygwin, and the changes made are very minor.

Yet geomview -run ./savi-dev/savi now fails on both ubuntu and cygwin,
while geomview -run savi to run the savi package works just fine. So,
it's something that has changed elsewhere, not sure what yet.

(Might this be an indication that piping control of geomview needs a
rethink? No idea.)

Lloyd Wood
http://savi.sf.net



On Monday, 10 June 2019, 03:29:03 GMT+10, <raj...@ij...> wrote: 



Try extracting files from the package without installing;
if there are separate patch files, you can see what they
are (and may need to apply them). At least some fedora
packages are like this.

Rajmund

On Sun, 9 Jun 2019, Lloyd Wood via geomview-users wrote:

> I'm dealing with the odd situation on linux where
> geomview -run savi
> works just fine if geomview and savi are installed as
> ubuntu packages, but if I compile savi 1.5.1 (matching
> the package) SaVi segfaults on first attempting to write to the
> pipe to geomview via fprintf.
>
>
> stdout is set up to point to geomview and dup'd, and there's
> a lot of error checking in that code to test for failures
> during setup. Those checks pass, but as soon as you fprintf
> to the pipe - boom, goodbye your compiled savi.
>
>
> This code hasn't changed (ie I'm not smart enough to change
> it) in years...
>
> Has something changed in stdlib or in how file pointers
>
> can be used and abused in gcc? Ideas to investigate  welcome.
>
> thanks
>
> Lloyd Wood
> http://savi.sf.net/