1. The forums will be archived and moved to a read only mode in about 2 weeks (mid march).

Solved Weird bug

Discussion in 'Help' started by Teamblocket, Feb 17, 2018.

  1. Teamblocket

    Teamblocket Zombie

    Messages:
    301
    GitHub:
    teamblocket
    When I start my server none of the commands or anything works. the server later disable its self without any warning or notice messages, a crash dump isn't created but i do get treated with this message in console
    Code:
    Segmentation fault: 11
    
     
  2. CupidonSauce173

    CupidonSauce173 Zombie

    Messages:
    298
    GitHub:
    cupidonsauce173
  3. Teamblocket

    Teamblocket Zombie

    Messages:
    301
    GitHub:
    teamblocket
    Devtools and my Core.
     
  4. CupidonSauce173

    CupidonSauce173 Zombie

    Messages:
    298
    GitHub:
    cupidonsauce173
    @Teamblocket Try to remove your Core and start your server.
     
  5. robske_110 (Tim)

    robske_110 (Tim) Wither Skeleton Poggit Reviewer

    Messages:
    1,342
    GitHub:
    robske110
    While it is possible (but shouldn't be) that his Core is causing a segfault it's more likely that his php bin has got problems.
    At what point of starting does the server segfault? (means what messages are there before the segfault)
     
    jasonwynn10 likes this.
  6. Teamblocket

    Teamblocket Zombie

    Messages:
    301
    GitHub:
    teamblocket
    I fixed error.
    This is what i was doing (Biggest typo)
    PHP:
    public function a(){
       
    $this->a();
    }
     
  7. robske_110 (Tim)

    robske_110 (Tim) Wither Skeleton Poggit Reviewer

    Messages:
    1,342
    GitHub:
    robske110
    Oh, the recursion segfault. I thought it used to only zend_mm_heap_corrupt?
    Good that you found it though!
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.