Power Debugging & Profiling Your PHP Apps

Transcript

1. Power  Debugging  &  Profiling   Your  PHP  Apps   Abu  Ashraf  Masnun  
2. WHAT’S  YOUR  STORY?   Let’s  share  experiences!  
3. Error  Display   •  Turn  on  error  display     •  Report  all  errors   •  E_ALL  |  E_STRICT   •  Don’t  ignore  those  “NoKce”  messages  
4. Print  &  Die   •  Output  something  and  then  terminate  the   script.     •  var_dump()     •  print_r()   •  Output  buffering  for  cleaner  output   •  debug_backtrace()  
5. Logging   •  Use  a  logging  library  (Monolog,  anyone?)   •  error_log()   •  mod_php  sets  stderr  to  apache  logs:   –  file_put_contents('php://stderr',  print_r($foo,  TRUE))   •  trigger_error()  &  set_error_handler()   Tail  your  logs:     tail  -­‐f  your_log_file_path  
6. InteresKng  Tools   •  FirePHP,  Chrome  Logger   •  Kint,  PHP  Debug  Bar  
7. THE  MOTHER  OF  ALL  DEBUGGER   Let’s  meet    
8. ConfiguraKon  
9. Netbeans  
10. Netbeans  
11. Netbeans  
12. PROFILING  LIKE  A  PRO  
13. Start  Profiling  
14. The  Cachegrind  Files  
15. Using  Webgrind  
16. @MASNUN   Feel  free  to  reach  out:     hap://masnun.me