Activating Toolbar Component Causes Segmentation Fault Or NotFoundException

[mesr]

Since CakePHP 2.4.3, adding the DebugKit.Toolbar component to a controller in my dev environment produces a PHP segmentation fault (as logged in /var/log/apache2/error.log) and a connection reset on the client (Firefox), unless CakePHP debug level is set to 0 (i.e. Configure::write('debug', 0) in app/Config/core.php), in which case the script doesn't crash and CakePHP returns the following flash message: "Error: The requested address '/my/project/webroot/' was not found on this server." along with some more details in app/tmp/logs/error.log:

2014-01-02 10:38:05 Error: [NotFoundException] Not Found
Request URL: /my/project/webroot/
Stack Trace:
#0 /base/path/to/project/lib/Cake/View/View.php(929): include()
#1 /base/path/to/project/lib/Cake/View/View.php(891): View->_evaluate('/base/path...', Array)
#2 /base/path/to/project/lib/Cake/View/View.php(460): View->_render('/base/path...')
#3 /base/path/to/project/lib/Cake/Controller/Controller.php(952): View->render('home', NULL)
#4 /base/path/to/project/app/Controller/PagesController.php(68): Controller->render('home')
#5 [internal function]: PagesController->display('home')
#6 /base/path/to/project/lib/Cake/Controller/Controller.php(490): ReflectionMethod->invokeArgs(Object(PagesController), Array)
#7 /base/path/to/project/lib/Cake/Routing/Dispatcher.php(185): Controller->invokeAction(Object(CakeRequest))
#8 /base/path/to/project/lib/Cake/Routing/Dispatcher.php(160): Dispatcher->_invoke(Object(PagesController), Object(CakeRequest), Object(CakeResponse))
#9 /base/path/to/project/app/webroot/index.php(108): Dispatcher->dispatch(Object(CakeRequest), Object(CakeResponse))
#10 {main}

Loading the plug-in without adding the component to a controller works just fine, no errors. I'm using PHP 5.3.10 and a bare, fresh install of CakePHP 2.4.3 and DebugKit 2.2.2. Any idea how to debug this?

[markstory]

I've had to use strace before to figure out why PHP is segfaulting. It is rarely fun. I'm not aware of any code in DebugKit that has ever caused a segfault before.

The 404 errors are also strange, are you maybe missing a view file? The stack trace is a bit suspicious.

[markstory]

Closing as there have been no additional reports of this, and no way to reproduce the issue.