" -1"运行php artisan时在app根目录中创建的文件

时间:2017-12-22 14:19:35

标签: php laravel xdebug artisan

我在Homestead上运行Laravel,每当我运行任何php artisan XXX命令时,都会在应用程序的根目录中创建名为-1的文件。

该文件的内容与以下内容类似:

Log opened at 2017-12-22 13:54:00
I: Connecting to configured address/port: 10.0.2.2:9000.
E: Time-out connecting to client. :-(
Log closed at 2017-12-22 13:54:00

我99%确定它与我在尝试使XDebug断点与artisan命令一起工作的失败尝试中所做的一些更改有关。我按照this回答中的建议export编辑了一些shell变量,但是当我运行export -p时,我看不到其中任何一个。

有没有人有类似的问题?什么设置可能导致这种行为?

1 个答案:

答案 0 :(得分:0)

根据LazyOne的建议,我找到了答案:

#include <gtk/gtk.h> int buttonState = 2; static void button_cb (GtkWidget *widget, gpointer data) { if (buttonState == 0) gtk_widget_set_name (widget, "btnFail"); else if (buttonState == 1) gtk_widget_set_name (widget, "btnNeutral"); else gtk_widget_set_name (widget, "btnSuccess"); buttonState = buttonState == 2 ? 0 : ++buttonState; } int main (int argc, char **argv) { gtk_init (&argc, &argv); GtkWidget *window = gtk_window_new (GTK_WINDOW_TOPLEVEL); gtk_window_set_default_size (GTK_WINDOW (window), 200, 200); g_signal_connect(window, "destroy", G_CALLBACK (gtk_main_quit), NULL); GtkWidget *button = gtk_button_new_with_label ("Click Me"); gtk_widget_set_name (button, "btnNeutral"); gtk_widget_set_valign (button, GTK_ALIGN_CENTER); gtk_widget_set_halign (button, GTK_ALIGN_CENTER); g_signal_connect (button, "clicked", G_CALLBACK (button_cb), NULL); gtk_container_add (GTK_CONTAINER (window), button); GtkCssProvider *provider = gtk_css_provider_new (); GdkDisplay *display = gdk_display_get_default (); GdkScreen *screen = gdk_display_get_default_screen (display); gtk_style_context_add_provider_for_screen (screen, GTK_STYLE_PROVIDER (provider), GTK_STYLE_PROVIDER_PRIORITY_USER); gtk_css_provider_load_from_data (GTK_CSS_PROVIDER (provider), "#btnNeutral {background:blue; color:white} #btnFail {background:red; color:white} #btnSuccess {background:green; color:white}", -1 , NULL); gtk_widget_show_all (window); gtk_main (); return 0; } 文件中的路径似乎必须是绝对的。所以而不是:

.ini

我必须将其设置为:

xdebug.remote_log=~/code/xdebug.log

现在它可以正常工作。