Hi Michael,

thanks for the report. I initially could not reproduce as this seems not to happen when generating Python bindings.

Here is a Dockerfile to check if this is fixed:

-----------------------------------------------------
FROM debian:sid
MAINTAINER Torsten Landschoff <tors...@debian.org>

RUN adduser maint --disabled-password --gecos "SWIG maintenance"

RUN apt-get update
RUN apt-get -yy install swig3.0

ADD https://raw.githubusercontent.com/swig/swig/8bc38dc0070740d1a4b1ec522f80c7e292a74850/Examples/test-suite/nested_scope.i /home/maint/
RUN chown maint:maint /home/maint/*

USER maint
WORKDIR /home/maint

# For some reason this works fine
RUN swig3.0 -c++ -python nested_scope.i

# But using Tcl or Ruby as target language leads to the crash
RUN swig3.0 -version
RUN swig3.0 -c++ -ruby nested_scope.i
RUN swig3.0 -c++ -tcl nested_scope.i

ENTRYPOINT ["/bin/bash", "-i"]
-----------------------------------------------------

Running this through "docker build", I get the following output:

torsten@horatio:~/debwork/swig-768280$ sudo docker build .
[...]
Removing intermediate container 0751a6438b2d
Step 10 : RUN swig3.0 -version
 ---> Running in 5c17530272ae

SWIG Version 3.0.2

Compiled with g++ [x86_64-unknown-linux-gnu]

Configured options: +pcre

Please see http://www.swig.org for reporting bugs and further information
 ---> 75497219552a
Removing intermediate container 5c17530272ae
Step 11 : RUN swig3.0 -c++ -ruby nested_scope.i
 ---> Running in 9d98770ffe45
Segmentation fault (core dumped)
INFO[0004] The command [/bin/sh -c swig3.0 -c++ -ruby nested_scope.i] returned a non-zero code: 139

So I can confirm this happens when generating Ruby or Tcl bindings. I did not check others apart from Python (which does not crash).

So far about that, now I have to get access to Subversion again. I moved my ssh key to a hardware token and currently my setup refuses to use it for SSH login.

Greetings, Torsten


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to