On Mon, Aug 11, 2014 at 4:22 PM, Pascal Chevrel <pascal.chev...@free.fr> wrote:
> Le 11/08/2014 16:10, Laruence a écrit : > > Hey: >> >> >> >> On Mon, Aug 11, 2014 at 10:07 PM, Pascal Chevrel <pascal.chev...@free.fr> >> wrote: >> >>> Le 01/08/2014 13:58, Pascal Chevrel a écrit : >>> >>> Hi >>>> >>>> Another bug I found: https://bugs.php.net/bug.php?id=67735 >>>> >>>> When running "composer update" on a project I participate in >>>> (https://github.com/framasoft/framadate), PHPNG crashes. >>>> >>>> Regards >>>> >>> >> >> are you able to get a backtrace? >> >> if yes, please paste the backtrace as a comment in that bug entry >> >> it will give us a useful help :) >> >> thanks >> > > Hi, > > I had looked at the instructions to provide a backtrace and they don't > target PHP devs but C devs and the instructions suppose a lot of knowledge > I don't have, sorry, I don't currently have time to invest in understanding > the instructions that are provided as they are not straightforward nor > detailed enough for people that don't compile PHP but just use the PPA :/ > > I do have though the dump file produced by ubuntu on crashing that is > 1.7MB big, I can copy paste the part that looks relevant to PHP in the bug > which looks like a hundred lines; although I am not entirely sure this is > what you guys are asking for. > > Regards, > > > Pascal > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > nope, as you was told in the bugreport(https://bugs.php.net/bug.php?id=67735), we need the backtrace generated from the core file. the core file is basically a dump of the memory from the crashed process we can't really use it without the environment which produced it, so we need you to follow the instructions from https://bugs.php.net/bugs-generating-backtrace.php and provide a backtrace from gdb (which produces something similar than what debug_backtrace does but for C applications). but at this point I start to think that it would be easier to ask you to tell us the exact composer version you are using, the exact composer command you are executing and to upload the composer.json and/or composer.lock you currently have so that maybe somebody else (who can create a backtrace) can reproduce the issue that way. -- Ferenc Kovács @Tyr43l - http://tyrael.hu
