Works for me. So better release 1.7.0 soon before I find something else.
My secret agenda is delaying it to r3000 :-P
On Wed, Aug 14, 2013 at 7:13 AM, Greg Hellings wrote:
> I have committed two fixes to Perl:
> One fixes the intermittent builds that I was experiencing. It turns out that
> CMake
I have committed two fixes to Perl:
One fixes the intermittent builds that I was experiencing. It turns out
that CMake and Swig were both generating files named 'Makefile' in the
build directory. Now the Perl files generate Makefile.perlswig instead.
The other fixes the seg fault on exit that was
Adding some more details:
main::(Perlbindingstest.pl:4): my $mgr = new Sword::SWMgr();
DB<1> l
4==>my $mgr = new Sword::SWMgr();
5: my $neu = $mgr->getModule("GerNeUe");
6: my $key = new Sword::SWKey("Genesis 1:1");
7: $neu->setKey($key);
8: print $neu->renderText(),"\n";
This is all I can get out of debugging...
Program received signal SIGSEGV, Segmentation fault.
0x7646ee73 in sword_SWKey___str__ (my_perl=, cv=)
at Sword.cxx:2360
2360return const_cast(self->getText());
Probably not helpful at all...
btw it's r2955.
On Mon,
With my little Perlprogramm I get a segmentation fault. I don't get
them with a similiar python programm, how would I debug these?
$ ./Perlbindingstest.pl
Im Anfang schuf Gott Himmel und Erde.
Segmentation fault
Perlbindingstest.pl:
#!/usr/bin/perl
use Sword;
my $mgr = new Sword::SWMgr();
my $n
