Composer: Symfony Signal 5 Fatal Error

[robertdown]

Composer version 1f2d331fd341897c9d54414a76b909beba9e3a59

I'm receiving this error when I try to run composer install, composer update, composer diagnose

Exception trace:
 () at phar:///usr/local/bin/composer/vendor/symfony/process/Symfony/Component/Process/Process.php:430
 Symfony\Component\Process\Process->wait() at phar:///usr/local/bin/composer/vendor/symfony/process/Symfony/Component/Process/Process.php:207
 Symfony\Component\Process\Process->run() at phar:///usr/local/bin/composer/src/Composer/Util/ProcessExecutor.php:61
 Composer\Util\ProcessExecutor->execute() at phar:///usr/local/bin/composer/src/Composer/Package/Loader/RootPackageLoader.php:192
 Composer\Package\Loader\RootPackageLoader->guessGitVersion() at phar:///usr/local/bin/composer/src/Composer/Package/Loader/RootPackageLoader.php:177
 Composer\Package\Loader\RootPackageLoader->guessVersion() at phar:///usr/local/bin/composer/src/Composer/Package/Loader/RootPackageLoader.php:57
 Composer\Package\Loader\RootPackageLoader->load() at phar:///usr/local/bin/composer/src/Composer/Factory.php:235
 Composer\Factory->createComposer() at phar:///usr/local/bin/composer/src/Composer/Factory.php:393
 Composer\Factory::create() at phar:///usr/local/bin/composer/src/Composer/Console/Application.php:175
 Composer\Console\Application->getComposer() at phar:///usr/local/bin/composer/src/Composer/Command/Command.php:50
 Composer\Command\Command->getComposer() at phar:///usr/local/bin/composer/src/Composer/Command/InstallCommand.php:59
 Composer\Command\InstallCommand->execute() at phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Command/Command.php:244
 Symfony\Component\Console\Command\Command->run() at phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Application.php:882
 Symfony\Component\Console\Application->doRunCommand() at phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Application.php:212
 Symfony\Component\Console\Application->doRun() at phar:///usr/local/bin/composer/src/Composer/Console/Application.php:117
 Composer\Console\Application->doRun() at phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Application.php:119
 Symfony\Component\Console\Application->run() at phar:///usr/local/bin/composer/src/Composer/Console/Application.php:83
 Composer\Console\Application->run() at phar:///usr/local/bin/composer/bin/composer:43
 require() at /usr/local/bin/composer:15

[Seldaek]

Could I see the exception message too not just the trace?

[robertdown]

[SymfonyComponentProcessExceptionRuntimeException]
The process has been signaled with signal "5".

[robertdown]

Any news on this? I rolled back to 1.0.0-alpha7 and it still isn't working. I can't even do a dry run install or update

[hakre]

@robertdown: Can you also share some details about your operating system? And did you use a previous version which worked? If so, which one?

[robertdown]

OS X, 10.7.5. I did use a previous version that worked, but I am unsure of the version.

I also have a production linux server running composer (successfully at the moment) - but it appears a coworker is running maintenance on the server at the moment so I can't get the composer version - I'll post it as soon as I can back in.

[robertdown]

Have we had any movement on this? It's crippling my workflow. I removed all remnants of composer including .composer, downloaded the latest copy from http://getcomposer.org/download/ using
curl -sS https://getcomposer.org/installer | php
moved the composer.phar to my project, ran php composer.php update and I still got the error.

[Seldaek]

@romainneutron any idea? Signal 5 is SIGTRAP, but I have no idea where that could come from.

@robertdown could you run it again with -vvv and paste the last CMD line above the exception? Just to see exactly which command gets killed like that.

[romainneutron]

Hello all,

it seems SIGTRAP is used for debugging/breakpoint/trace purposes. What PHP version are you using ? Are you using any debugger or profiler ?

[robertdown]

PHP 5.4.16. I do have a debugger installed, but I've always had it installed and has never caused any issue with composer.

() at phar:///usr/local/zend/apache2/htdocs/mc-deployment/composer.phar/vendor/symfony/process/Symfony/Component/Process/Process.php:428

[cs278]

@robertdown That's part of the PHP stack trace, the last command with be the last line in the output beginning with Executing command.

[robertdown]

Couldn't find Executing command

[romainneutron]

Hello Robert,

I'm asking you if you got a debugger because SIGTRAP is generally used by debuggers. If you think your debugger has nothing to do with your issue, well, let's go ignoring this.

It would be nice to collaborate and try doing some tests without this debugger. This issue is not so common, I do believe it's not about composer but about your configuration. I may be wrong, meanwhile let's cooperate or we might not solve this issue.

[robertdown]

Ok, I disabled the debugger and restarted my server and I'm still getting
the same error. I've been racking my brain to see if I can remember anything
I may have changed recently, but I can't think of anything.

Regards,
Robert Down

From: Romain Neutron [email protected]
Reply-To: composer/composer
hub.com>
Date: Friday, August 16, 2013 6:24 PM
To: composer/composer [email protected]
Cc: "Robert Down, Jr" [email protected]
Subject: Re: [composer] Symfony Signal 5 Fatal Error (#2146)

Hello Robert,

I'm asking you if you got a debugger because SIGTRAP is generally used by
debuggers. If you think your debugger has nothing to do with your issue, well,
let's go ignoring this.

It would be nice to collaborate and try doing some tests without this
debugger. This issue is not so common, I do believe it's not about composer
but about your configuration. I may be wrong, meanwhile let's cooperate or we
might not solve this issue.

—
Reply to this email directly or view it on GitHub
https://github.com/composer/composer/issues/2146#issuecomment-22797852 .

[romainneutron]

@Seldaek Is there an easy way to download older version of composer that use symfony/process 2.2 and that would work with the current packagist API, for testing ?

[robertdown]

I just tried cloning the composer repo and building 3ffad59719bd94987813ea1872001619200c24a0 (This version was from another server I manage where composer is working properly).

Of course, to install composer from source you have to use composer.phar...... no dice

[Seldaek]

Of course, to install composer from source you have to use
composer.phar...... no dice

You can install/build a phar (run bin/compile) on another machine and
then transfer the phar to the broken server to test.

[Seldaek]

Couldn't find |Executing command|

Sorry about the missing command in the output, that was my bad. If you
try with the latest phar it should show up now.

[robertdown]

reading ./composer.json
Executing command (CWD): git describe --exact-match --tags
Reading ./composer.json
Executing command (CWD): git describe --exact-match --tags

sidebar: why is it reading the file twice?

[Seldaek]

What command are you running exactly? And what's the full output? I
don't get two reads, but well it's possible that it would read twice for
various reasons.

[Seldaek]

OK so first of all it seems that it runs fine the first time and not the
second even though everything is the same. That's weird.

Second weird thing is it's running it twice and loading twice.

Can you share your composer.json? Because even if I run the same command
as you do I don't get this double loading thing.

As a side-note. I suppose that if you run the command yourself in the
same directory as you ran composer, it goes fine?

git describe --exact-match --tags

[robertdown]

Sorry about that last comment, I sent it from my email and I guess github doesn't parse emails through GFM

My composer file won't do you much good, we have closed-source repos we pull from.

But, that doesn't matter…. This part is far more interesting

rdown [21:27] mc-deployment $ git describe --exact-match --tags
fatal: no tag exactly matches 'b11cb924e52b488ff68f53b37b30a73d38dbdae8'

BUT! If I checkout a tag (1.3.1 in this case) I get the following

rdown [21:29] mc-deployment $ git describe --exact-match --tags
1.3.1

And it still fails, below is the trace when I'm on tag 1.3.1

 [Symfony\Component\Process\Exception\RuntimeException]
  The process has been signaled with signal 5.

Exception trace:
 () at
phar:///usr/local/zend/apache2/htdocs/mc-deployment/composer.phar/vendor/sym fony/process/Symfony/Component/Process/Process.php:428
 Symfony\Component\Process\Process->wait() at
phar:///usr/local/zend/apache2/htdocs/mc-deployment/composer.phar/vendor/sym
fony/process/Symfony/Component/Process/Process.php:204
 Symfony\Component\Process\Process->run() at
phar:///usr/local/zend/apache2/htdocs/mc-deployment/composer.phar/src/Compos
er/Util/ProcessExecutor.php:61
 Composer\Util\ProcessExecutor->execute() at
phar:///usr/local/zend/apache2/htdocs/mc-deployment/composer.phar/src/Compos
er/Package/Loader/RootPackageLoader.php:192
 Composer\Package\Loader\RootPackageLoader->guessGitVersion() at
phar:///usr/local/zend/apache2/htdocs/mc-deployment/composer.phar/src/Compos
er/Package/Loader/RootPackageLoader.php:177
 Composer\Package\Loader\RootPackageLoader->guessVersion() at
phar:///usr/local/zend/apache2/htdocs/mc-deployment/composer.phar/src/Compos
er/Package/Loader/RootPackageLoader.php:57
 Composer\Package\Loader\RootPackageLoader->load() at
phar:///usr/local/zend/apache2/htdocs/mc-deployment/composer.phar/src/Compos
er/Factory.php:237
 Composer\Factory->createComposer() at
phar:///usr/local/zend/apache2/htdocs/mc-deployment/composer.phar/src/Compos
er/Factory.php:408
 Composer\Factory::create() at
phar:///usr/local/zend/apache2/htdocs/mc-deployment/composer.phar/src/Compos
er/Console/Application.php:175
 Composer\Console\Application->getComposer() at
phar:///usr/local/zend/apache2/htdocs/mc-deployment/composer.phar/src/Compos
er/Command/Command.php:50
 Composer\Command\Command->getComposer() at
phar:///usr/local/zend/apache2/htdocs/mc-deployment/composer.phar/src/Compos
er/Command/UpdateCommand.php:63
 Composer\Command\UpdateCommand->execute() at
phar:///usr/local/zend/apache2/htdocs/mc-deployment/composer.phar/vendor/sym
fony/console/Symfony/Component/Console/Command/Command.php:244
 Symfony\Component\Console\Command\Command->run() at
phar:///usr/local/zend/apache2/htdocs/mc-deployment/composer.phar/vendor/sym
fony/console/Symfony/Component/Console/Application.php:897
 Symfony\Component\Console\Application->doRunCommand() at
phar:///usr/local/zend/apache2/htdocs/mc-deployment/composer.phar/vendor/sym
fony/console/Symfony/Component/Console/Application.php:191
 Symfony\Component\Console\Application->doRun() at
phar:///usr/local/zend/apache2/htdocs/mc-deployment/composer.phar/src/Compos
er/Console/Application.php:117
 Composer\Console\Application->doRun() at
phar:///usr/local/zend/apache2/htdocs/mc-deployment/composer.phar/vendor/sym
fony/console/Symfony/Component/Console/Application.php:121
 Symfony\Component\Console\Application->run() at
phar:///usr/local/zend/apache2/htdocs/mc-deployment/composer.phar/src/Compos
er/Console/Application.php:83
 Composer\Console\Application->run() at
phar:///usr/local/zend/apache2/htdocs/mc-deployment/composer.phar/bin/compos
er:43
 require() at /usr/local/zend/apache2/htdocs/mc-deployment/composer.phar:15

[Seldaek]

Yes that is the expected behavior (the fatal). It is caught and if the
process fails we just don't read the output.

If you could give me a copy of your composer.json with redacted URLs
though it might still be useful to figure out why there is this
double-loading of composer.json. It doesn't have to be installable for
me since this happens very early in the bootstrap process it seems.
Alternatively you can email it to j.[email protected] if you don't like
to have it public.

[robertdown]

I understand why it'd fail if the git describe fails, but when I moved to the tag it still failed, even though git describe passed, below it a redacted composer.json file

{
    "license": "proprietary",
    "keywords" : [],
    "require" : {
        "redacted" : "1.3",
        "redacted" : "1.3.5"
    },
    "autoload" : {
        "psr-0" : {
            "Application\\" : "src/"
        }
    },
    "repositories" : [{
            "type" : "vcs",
            "url" : "[email protected]:redacted/redacted.git"
        }, {
            "type" : "vcs",
            "url" : "[email protected]:redacted/redacted.git"
        }
    ]
}

[Seldaek]

Thanks. No luck though :/ This is really puzzling.

[robertdown]

Could it be a problem with one of the repos we pull from?

Can you replicate the error?

Regards,
Robert Down

From: Jordi Boggiano [email protected]
Reply-To: composer/composer
hub.com>
Date: Friday, August 16, 2013 9:54 PM
To: composer/composer [email protected]
Cc: "Robert Down, Jr" [email protected]
Subject: Re: [composer] Symfony Signal 5 Fatal Error (#2146)

Thanks. No luck though :/ This is really puzzling.

—
Reply to this email directly or view it on GitHub
https://github.com/composer/composer/issues/2146#issuecomment-22803565 .

[Seldaek]

Nope I can't reproduce, and I really doubt it's related to your repos,
but you could easily check that by removing the custom repos and see if
it still loads twice and fails.

[robertdown]

Do you have any insight on the Signal 5 error?

I've stripped down my composer.json file bare miminum – all it requires is
monolog, just a random package I pulled from packagist just now, still no
luck.

Regards,
Robert Down

From: Jordi Boggiano [email protected]
Reply-To: composer/composer
hub.com>
Date: Friday, August 16, 2013 10:04 PM
To: composer/composer [email protected]
Cc: "Robert Down, Jr" [email protected]
Subject: Re: [composer] Symfony Signal 5 Fatal Error (#2146)

Nope I can't reproduce, and I really doubt it's related to your repos,
but you could easily check that by removing the custom repos and see if
it still loads twice and fails.

—
Reply to this email directly or view it on GitHub
https://github.com/composer/composer/issues/2146#issuecomment-22803730 .

[Seldaek]

Nope sorry but I really have no clue what's causing this.

[hakre]

debugging with dbg should reveal this. so in case the reporter wants to find out more, why not within a dbg session and stopping on that signal?

[romainneutron]

Hello,

If I understand correctly the git describe --exact-match --tags fails because a SIGTRAP signal ?
Which git is used (which git output) ? Is it the one provided by Xcode ? Is this a custom build ?

[robertdown]

I believe that is the case, yet. I'm running a custom build of git (usr/bin/git version 1.8.3.4)

[robertdown]

Checking platform settings: OK
Checking http connectivity: Downloading https://packagist.org/packages.json
OK
Reading ./composer.json
Executing command (CWD): git describe --exact-match --tags
Reading ./composer.json
Executing command (CWD): git describe --exact-match --tags



  [Symfony\Component\Process\Exception\RuntimeException]
  The process has been signaled with signal "5".



Exception trace:
 () at phar:///usr/local/bin/composer/vendor/symfony/process/Symfony/Component/Process/Process.php:428
 Symfony\Component\Process\Process->wait() at phar:///usr/local/bin/composer/vendor/symfony/process/Symfony/Component/Process/Process.php:204
 Symfony\Component\Process\Process->run() at phar:///usr/local/bin/composer/src/Composer/Util/ProcessExecutor.php:61
 Composer\Util\ProcessExecutor->execute() at phar:///usr/local/bin/composer/src/Composer/Package/Loader/RootPackageLoader.php:192
 Composer\Package\Loader\RootPackageLoader->guessGitVersion() at phar:///usr/local/bin/composer/src/Composer/Package/Loader/RootPackageLoader.php:177
 Composer\Package\Loader\RootPackageLoader->guessVersion() at phar:///usr/local/bin/composer/src/Composer/Package/Loader/RootPackageLoader.php:57
 Composer\Package\Loader\RootPackageLoader->load() at phar:///usr/local/bin/composer/src/Composer/Factory.php:228
 Composer\Factory->createComposer() at phar:///usr/local/bin/composer/src/Composer/Factory.php:399
 Composer\Factory::create() at phar:///usr/local/bin/composer/src/Composer/Console/Application.php:175
 Composer\Console\Application->getComposer() at phar:///usr/local/bin/composer/src/Composer/Command/Command.php:50
 Composer\Command\Command->getComposer() at phar:///usr/local/bin/composer/src/Composer/Command/DiagnoseCommand.php:65
 Composer\Command\DiagnoseCommand->execute() at phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Command/Command.php:244
 Symfony\Component\Console\Command\Command->run() at phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Application.php:897
 Symfony\Component\Console\Application->doRunCommand() at phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Application.php:191
 Symfony\Component\Console\Application->doRun() at phar:///usr/local/bin/composer/src/Composer/Console/Application.php:117
 Composer\Console\Application->doRun() at phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Application.php:121
 Symfony\Component\Console\Application->run() at phar:///usr/local/bin/composer/src/Composer/Console/Application.php:83
 Composer\Console\Application->run() at phar:///usr/local/bin/composer/bin/composer:43
 require() at /usr/local/bin/composer:15


diagnose

[romainneutron]

Can you try to run the same command with XCode git provided with command line tools (located in /usr/bin/git) ?

[robertdown]

/usr/bin/git points to my custom git install. I really don't think this is a git issue, but I'm really confused now, I just did a full reinstall of apache and PHP and still nothing.

[romainneutron]

It seems that it is the git command that is killed by a SIGTRAP. Forum users reported some unexpected SIGTRAP signals in programs compiled with buggy gcc versions.

[robertdown]

Ok, I reinstalled Xcode's command line tools which brought me back to git version 1.7.12.4 (Apple Git-37) and this solved the problem. So apparently I built git with a buggy version of gcc. Do we have any reason to believe that composer isn't working with git 1.8.3.4?

[Seldaek]

Not that I know of.. but it's not like I have any numbers on this.

[romainneutron]

Glad we solved this !

I'm running git version 1.8.3.1 installed via homebrew and gcc i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00) and I do not encounter the issue

[romainneutron]

just bumped to 1.8.3.4, still no problem

[Seldaek]

Closing since it seems we can't help here. Hopefully it's been resolved on your end.

[ifox]

I have the same issue on 10.9.1 after composer self-update. I tried to reinstall xcode command line tools and to install git from official package. Still getting the same error.

[mgoolie]

I had the same issue it was being caused by svn, version 1.7.10 (r1485443). I renamed svn in /usr/bin to /usr/bin/svn.orig and it resolved my issues.

Reading ./composer.json
Executing command (CWD): git describe --exact-match --tags
Executing command (CWD): git branch --no-color --no-abbrev -v
Executing command (CWD): hg branch
Executing command (CWD): svn info --xml
Reading ./composer.json
Executing command (CWD): git describe --exact-match --tags
Executing command (CWD): git branch --no-color --no-abbrev -v
Executing command (CWD): hg branch
Executing command (CWD): svn info --xml

[SymfonyComponentProcessExceptionRuntimeException]
The process has been signaled with signal "5".

Exception trace:
() at phar:///Users/mgoolie/composer.phar/vendor/symfony/process/Symfony/Component/Process/Process.php:330
SymfonyComponentProcessProcess->wait() at phar:///Users/mgoolie/composer.phar/vendor/symfony/process/Symfony/Component/Process/Process.php:200
SymfonyComponentProcessProcess->run() at phar:///Users/mgoolie/composer.phar/src/Composer/Util/ProcessExecutor.php:61
ComposerUtilProcessExecutor->execute() at phar:///Users/mgoolie/composer.phar/src/Composer/Package/Loader/RootPackageLoader.php:307
ComposerPackageLoaderRootPackageLoader->guessSvnVersion() at phar:///Users/mgoolie/composer.phar/src/Composer/Package/Loader/RootPackageLoader.php:187
ComposerPackageLoaderRootPackageLoader->guessVersion() at phar:///Users/mgoolie/composer.phar/src/Composer/Package/Loader/RootPackageLoader.php:57
ComposerPackageLoaderRootPackageLoader->load() at phar:///Users/mgoolie/composer.phar/src/Composer/Factory.php:239
ComposerFactory->createComposer() at phar:///Users/mgoolie/composer.phar/src/Composer/Factory.php:448
ComposerFactory::create() at phar:///Users/mgoolie/composer.phar/src/Composer/Console/Application.php:176
ComposerConsoleApplication->getComposer() at phar:///Users/mgoolie/composer.phar/src/Composer/Command/Command.php:51
ComposerCommandCommand->getComposer() at phar:///Users/mgoolie/composer.phar/src/Composer/Command/DumpAutoloadCommand.php:44
ComposerCommandDumpAutoloadCommand->execute() at phar:///Users/mgoolie/composer.phar/vendor/symfony/console/Symfony/Component/Console/Command/Command.php:241
SymfonyComponentConsoleCommandCommand->run() at phar:///Users/mgoolie/composer.phar/vendor/symfony/console/Symfony/Component/Console/Application.php:892
SymfonyComponentConsoleApplication->doRunCommand() at phar:///Users/mgoolie/composer.phar/vendor/symfony/console/Symfony/Component/Console/Application.php:191
SymfonyComponentConsoleApplication->doRun() at phar:///Users/mgoolie/composer.phar/src/Composer/Console/Application.php:117
ComposerConsoleApplication->doRun() at phar:///Users/mgoolie/composer.phar/vendor/symfony/console/Symfony/Component/Console/Application.php:121
SymfonyComponentConsoleApplication->run() at phar:///Users/mgoolie/composer.phar/src/Composer/Console/Application.php:83
ComposerConsoleApplication->run() at phar:///Users/mgoolie/composer.phar/bin/composer:43
require() at /Users/mgoolie/composer.phar:15

dump-autoload [-o|--optimize]

[palypster]

"This problem should only show itself if you have a PHP script that is calls system("svn") .
It happens because OS X local svn requires the local libsasl installed, but zend's PHP uses its own libsasl build. However, svn and PHP don't share the same address space, just the same environment, so all we need is to give each one the environment it wants."

(from http://forums.zend.com/viewtopic.php?f=8&t=107973#p202868)

Basically what helped me was to add this line:

putenv("DYLD_LIBRARY_PATH=''");

in the top of the Process.php file of the composer.

[orlissenberg]

Cheers!

[otherjohn]

I still get this error and don't know how to put that variable in the process file.
I tried setting it as an environmental variable and it still doesn't work.
Any idea?

on a mac, using php from MAMP and latest build of composer.
I get the error anytime doing a update or install.

Mac OS X 10.9.2
which php /Applications/MAMP/bin/php/php5.4.19/bin/php
my .zshrc file
export PATH="/Applications/MAMP/bin/php/php5.4.19/bin:$PATH"
alias composer="php /Volumes/Boot/usr/local/bin/composer.phar"

[WendyMcF]

Thanks, this worked for me:
$brew install svn
$brew link --overwrite subversion

[otherjohn]

this worked for me too!:
$brew install svn
$brew link --overwrite subversion

[onursahin]

You should update your mac version become Maverick and then install and update composer.

[thinsoldier]

More info for anyone else still encountering bugs like this one.

Before running into this problem with composer and SymfonyComponentProcess I encountered it while working on something else involving basic exec() usage.

exec("git log",$output); print_r($output);

This was returning nothing while other commands like

exec("ls",$output); print_r($output);

were working fine.

I added 2>&1 to the end of my commands which apparently allows php to receive both the stderror content when unsuccessful as well as stdout when successful.

exec('git log 2>&1', $output); print_r($output);

Now I could see the actual error message from git:

dyld: lazy symbol binding failed: Symbol not found: _iconv_open
Referenced from: /Library/Developer/CommandLineTools/usr/bin/git
Expected in: /Applications/XAMPP/xamppfiles/lib/libiconv.2.dylib

dyld: Symbol not found: _iconv_open
Referenced from: /Library/Developer/CommandLineTools/usr/bin/git
Expected in: /Applications/XAMPP/xamppfiles/lib/libiconv.2.dylib

At this point I realized the culprit was something related to some "configuration thing" within XAMPP.

So a command like git log works from terminal but not from php exec().

I exported the environments to text files for closer inspection.

printenv > ./env_php.txt - ran via php exec
printenv > ./env_terminal - ran from command line

Comparing those 2 files I saw that this environment variable:
DYLD_LIBRARY_PATH=/Applications/XAMPP/xamppfiles/lib:/Applications/XAMPP/xamppfiles/lib
was present in the environment php runs in.

It comes from:
/Applications/XAMPP/xamppfiles/bin/envvars
/Applications/XAMPP/xamppfiles/bin/envvars-std

I'd imagine some people using wamp, xampp or other *amp packages might have similar issues.

So now whether I'm using basic exec() or some library that eventually uses SymfonyComponentProcess (like gitter) all I have to do is add unset DYLD_LIBRARY_PATH
to the beginning of my command/bash script
or use anywhere early in my php code to avoid the problem.

[ghost]

i'm having this issue on centos 6 with symfony 2.6.0
symfony 2.5.12 works fine

any help

[acady]

I have this issue on OS X 10.10 with AMPPS, Apple-Git55. Any help is welcome!

[SymfonyComponentProcessExceptionRuntimeException]
The process has been signaled with signal "5".

Exception trace:
() at phar:///usr/local/bin/composer/vendor/symfony/process/Symfony/Component/Process/Process.php:367
SymfonyComponentProcessProcess->wait() at phar:///usr/local/bin/composer/vendor/symfony/process/Symfony/Component/Process/Process.php:210
SymfonyComponentProcessProcess->run() at phar:///usr/local/bin/composer/src/Composer/Util/ProcessExecutor.php:62
ComposerUtilProcessExecutor->execute() at phar:///usr/local/bin/composer/src/Composer/Package/Loader/RootPackageLoader.php:325
ComposerPackageLoaderRootPackageLoader->guessSvnVersion() at phar:///usr/local/bin/composer/src/Composer/Package/Loader/RootPackageLoader.php:193
ComposerPackageLoaderRootPackageLoader->guessVersion() at phar:///usr/local/bin/composer/src/Composer/Package/Loader/RootPackageLoader.php:59
ComposerPackageLoaderRootPackageLoader->load() at phar:///usr/local/bin/composer/src/Composer/Factory.php:268
ComposerFactory->createComposer() at phar:///usr/local/bin/composer/src/Composer/Factory.php:486
ComposerFactory::create() at phar:///usr/local/bin/composer/src/Composer/Console/Application.php:222
ComposerConsoleApplication->getComposer() at phar:///usr/local/bin/composer/src/Composer/Command/Command.php:53
ComposerCommandCommand->getComposer() at phar:///usr/local/bin/composer/src/Composer/Command/InstallCommand.php:82
ComposerCommandInstallCommand->execute() at phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Command/Command.php:257
SymfonyComponentConsoleCommandCommand->run() at phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Application.php:874
SymfonyComponentConsoleApplication->doRunCommand() at phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Application.php:195
SymfonyComponentConsoleApplication->doRun() at phar:///usr/local/bin/composer/src/Composer/Console/Application.php:146
ComposerConsoleApplication->doRun() at phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Application.php:126
SymfonyComponentConsoleApplication->run() at phar:///usr/local/bin/composer/src/Composer/Console/Application.php:82
ComposerConsoleApplication->run() at phar:///usr/local/bin/composer/bin/composer:43
require() at /usr/local/bin/composer:25

[acady]

Sorry, I missed one small note:
"I had the same issue it was being caused by svn, version 1.7.10 (r1485443). I renamed svn in /usr/bin to /usr/bin/svn.orig and it resolved my issues."
solved it.

[ghost]

finally the issue is found. Thanks to Rackspace support staff Cristian Banciu and Mike Bostic

Cause:
Latest newrelic php agent 4.23.1.107 causes seg fault when used with symfony 2.6.0 or above with process component. newrelic.browser_monitoring.auto_instrument = 0 didn't help

Solution:
finally i downgraded newrelic php agent to 4.21.0.97-1 and all work fine

[trkoch]

Make sure your installation of Git is compatible with your system. To verify execute git describe --exact-match --tags.

[bgarrison25]

Hey guys, I have gone through this issue top to bottom and implemented all suggested fixes and am still getting this issue on Mac OSX 10.10 when installing a laravel app our company has made. I am the only developer using Max OSX and all others have no issue. Here is the output of composer install --vvv

post-install-cmd: php artisan clear-compiled


  [Symfony\Component\Process\Exception\RuntimeException]
  The process has been signaled with signal "5".


Exception trace:
 () at phar:///usr/local/bin/composer/vendor/symfony/process/Process.php:375
 Symfony\Component\Process\Process->wait() at phar:///usr/local/bin/composer/vendor/symfony/process/Process.php:203
 Symfony\Component\Process\Process->run() at phar:///usr/local/bin/composer/src/Composer/Util/ProcessExecutor.php:62
 Composer\Util\ProcessExecutor->execute() at phar:///usr/local/bin/composer/src/Composer/EventDispatcher/EventDispatcher.php:204
 Composer\EventDispatcher\EventDispatcher->doDispatch() at phar:///usr/local/bin/composer/src/Composer/EventDispatcher/EventDispatcher.php:94
 Composer\EventDispatcher\EventDispatcher->dispatchScript() at phar:///usr/local/bin/composer/src/Composer/Installer.php:337
 Composer\Installer->run() at phar:///usr/local/bin/composer/src/Composer/Command/InstallCommand.php:134
 Composer\Command\InstallCommand->execute() at phar:///usr/local/bin/composer/vendor/symfony/console/Command/Command.php:259
 Symfony\Component\Console\Command\Command->run() at phar:///usr/local/bin/composer/vendor/symfony/console/Application.php:844
 Symfony\Component\Console\Application->doRunCommand() at phar:///usr/local/bin/composer/vendor/symfony/console/Application.php:192
 Symfony\Component\Console\Application->doRun() at phar:///usr/local/bin/composer/src/Composer/Console/Application.php:189
 Composer\Console\Application->doRun() at phar:///usr/local/bin/composer/vendor/symfony/console/Application.php:123
 Symfony\Component\Console\Application->run() at phar:///usr/local/bin/composer/src/Composer/Console/Application.php:99
 Composer\Console\Application->run() at phar:///usr/local/bin/composer/bin/composer:43
 require() at /usr/local/bin/composer:24

install [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--no-plugins] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--ignore-platform-reqs] [--] [<packages>]...

Trace/BPT trap: 5

[okwebsite]

hi , i have error when install composer with osx el capitano v10.11 , i have mamp v 4.1.1 in osx and php v7 .
[SymfonyComponentProcessExceptionRuntimeException]
The process has been signaled with signal "5".
I attach the photo error
https://www.photobox.co.uk/my/photo/full?photo_id=9780357510

[emri99]

Got same error on OSX capitano too.

$ composer -vvv
Reading ./composer.json
Loading config file ./composer.json
Checked CA file /private/var/folders/89/7r_blf851pnb9w8rg22v6yt00000gn/T/composer-cacert-e62a07e61e5870effa81b430e1900778943c228bd7da1259dd6a955ee2262b47.pem: valid
Executing command (.../src/_tests/php-cs-fixer-config): git branch --no-color --no-abbrev -v
Executing command (.../src/_tests/php-cs-fixer-config): git describe --exact-match --tags
Executing command (.../src/_tests/php-cs-fixer-config): git log --pretty="%H" -n1 HEAD
Executing command (.../src/_tests/php-cs-fixer-config): hg branch
Executing command (.../src/_tests/php-cs-fixer-config): fossil branch list
Executing command (.../src/_tests/php-cs-fixer-config): fossil tag list
Executing command (.../src/_tests/php-cs-fixer-config): svn info --xml


  [Symfony\Component\Process\Exception\RuntimeException]  
  The process has been signaled with signal "5".          

$ svn
dyld: Library not loaded: /usr/lib/libcrypto.35.dylib
  Referenced from: /Library/Developer/CommandLineTools/usr/lib/libserf-1.0.dylib
  Reason: image not found
[1]    5221 trace trap  svn

So it's svn the problem.
But as I don't need svn, moving binary executable resolve this case.

mv /usr/bin/svn /usr/bin/svn-bak

[dnrobin]

@emri99 i confirm this is exactly what the problem was for me too. svn was not installed properly. Getting rid of the binary does allow composer to continue installation of dependency.

[deondazy]

This worked for me:
$brew install svn
$brew link --overwrite subversion

[softnayr]

works on me.

@deondazy thanks man

[PhilippeDunbar]

I had this problem too, spent about 3 hours trying to track it down. @deondazy solution fixed it for me as well. Thanks @emri99 for pointing out the SVN error.

Three potential solutions for this.

1. Add SVN to dependencies for homebrew installs. (easy, and would probably solve for most people)
2. A more verbose error for SVN errors.
3. git fallback (or use SVN as the fallback since git is more popular)

I'm not familiar with composer's codebase, but I'm willing to take a look into the feasibility of my suggestions.

[RingRan]

thanks to @PhilippeDunbar
I fix the problem in mac.
brew install svn.

[lukasfischer]

brew reinstall subversion

[azizultex]

$brew upgrade subversion
$brew link --overwrite subversion

Fixed my problem