On Wed, 28 May 2008, Andrew Johnson wrote:
> tiger% ./parrot -t t/dynoplibs/myops_3.pir
> 0 print "neither here\n"
> neither here
> 2 hcf
> Segmentation fault
Welcome to the club of people who've wasted time chasing this particularly
silly test. 'hcf' is supposed to stand for 'halt an
tiger% ./parrot -t t/dynoplibs/myops_3.pir
0 print "neither here\n"
neither here
2 hcf
Segmentation fault
When run under a debugger, it looks like this:
(dbx) run -t t/dynoplibs/myops_3.pir
Running: parrot -t t/dynoplibs/myops_3.pir
(process id 15185)
Reading myops_ops.so
0 print
On Tuesday 27 May 2008 10:15:45 Andrew Johnson wrote:
> Environment:
> Parrot SVN revision 27839
> Sun Ultra-40 M2, dual-core AMD Opteron CPU.
> Sun Solaris 10 (SunOS 5.10)
> Sun Studio 12
>
> I had to apply the following patch to get parrot to compile on the above
> setup;
Please try; ./parrot -t t/dynoplibs/myops_3.pir
And tell us if it's blocked while executing the "hcf" opcode.
The proposed change looks good to me, others C compilers can have the
same problem with returning a void result.
--
Salu2
