Re: CLI Crash Bug

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Keith Davis in php.windows (Sat, 20 Jul 2013 07:14:39 -0500):
>We are trying to move to 5.5, but are stopped by this bug which we reported:
>
>https://bugs.php.net/bug.php?id=65247

A tip: there is yet another way to get backtraces. I once used it to
track segfaults in httpd.exe, but there is a chance it will also work
with php.exe.

Description here: https://bugs.php.net/bugs-generating-backtrace.php
Versions for debugging 32-bits and 64-bits programs can be found here:
http://x32.elijst.nl/gdb.zip

Usage something like:
gdb php.exe
(gdb) run anyscript.php

Or you can run php interactively. Simple example is php -r exit():

D:\phpdev\php54nts.x32>gdb32.exe php.exe
GNU gdb (GDB) 7.5.1
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show
copying" and "show warranty" for details.
This GDB was configured as "i686-w64-mingw32".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from D:\phpdev\php54nts.x32\php.exe...(no debugging
symbols found)...done.

(gdb) run -r exit();
Starting program: D:\phpdev\php54nts.x32\php.exe -r exit();
[New Thread 3024.0x1314]
[New Thread 3024.0x904]
[Inferior 1 (process 3024) exited normally]
(gdb)

After a crash 'bt' at the (gdb) prompt should give you a backtrace.

Jan

-- 
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php





[Index of Archives]     [PHP Home]     [PHP Users]     [PHP Database Programming]     [PHP Install]     [Kernel Newbies]     [Yosemite Forum]     [PHP Books]

  Powered by Linux