child pid # exit signal bus error (10)

[Soma]

I'm creating a new Fieldtype, or trying to and run into a problem that doesn't seem PW related, but it's really strange.

I only happens when I add a new Inputfield module (not happens with other types!) if the error wouldn't be strangely enough already added Inputfield module seem to work. I found some infos out there but all seem not to be related and it seems like a apache/php/hardware problem. I'm lost

from apache error_log:

[Fri Jul 26 14:51:29 2013] [notice] child pid 584 exit signal Bus error (10)

[Fri Jul 26 14:51:30 2013] [notice] child pid 525 exit signal Bus error (10)

[Fri Jul 26 14:51:30 2013] [notice] child pid 524 exit signal Bus error (10)

[Fri Jul 26 14:52:31 2013] [notice] child pid 586 exit signal Bus error (10)

[Fri Jul 26 14:55:19 2013] [notice] child pid 630 exit signal Bus error (10)

[Fri Jul 26 14:55:52 2013] [notice] child pid 523 exit signal Bus error (10)

[Fri Jul 26 14:57:36 2013] [notice] child pid 589 exit signal Bus error (10)

[Fri Jul 26 15:02:19 2013] [notice] child pid 3120 exit signal Bus error (10)

 

I first thought it's a syntax error or something but after hour of trying it's all right and when I try to create a test Inputfield it happens again.

[DaveP]

I am by no means an expert, but searching around a bit suggests a segfault. Fixes include:

1. restart Apache
2. reseat memory (if you have access)

[Soma]

Thanks but that's a common routine check, already tried "everything" possible (usual tasks).

[Soma]

I'm on a MacOSX 10.6.8. XAMPP 1.7.3. PHP 5.3.1.

I changed PW version, no luck

tried another install, no luck

tried a plain php class not extending Inputfield, no error

There's no syntax faults for sure

Doesn't happen when adding new class extending Fieldtype or Process

[alevine]

That's got to be maddening!   All I could find were comments about variables missing their $ identifier, and maybe launching apache with an -x and using truss.  :/

Guess it's time to start blocking out segments of code in the new module and poor-man debug what's breaking.

Keep us posted, please.

[Soma]

Thanks alevine, but there's no syntax error or problem, the problem seems just creating a new class extending Inputfield. 

For example:

<?php

class InputfieldLinkList extends Inputfield {

    public static function getModuleInfo() {
        return array(
            'title' => __('Link List', __FILE__),
            'version' => 1,
            'summary' => __('Provides an administrative interface for working with link lists', __FILE__),
            'requires' => 'FieldtypeLinkList'
            );
    }

    public function render() {
        return "<div id='linklist_{$this->id}'>test</div>";
    }
}

So it somehow happens in Inputfield class, but there's dozens of Inputfield modules that are there working.... yeah it's mad.

[ryan]

Are you running an opcode cache (APC?). If so, put this in a PHP file and run it:

<?php apc_clear_cache(); 

I have no idea if that's the problem. But any time I get weird/inexplicable behavior from PHP, that usually fixes it. 

If that's not it, then it seems like the only thing different about your module from others would be the name. Hard to imagine it could be an issue, but I would try renaming it, just in case.

If not that: Turn off computer. Wait 30 seconds. Turn on computer?