5 Commits

Author	SHA1	Message	Date
Aaron Lehmann	a4c68ee857	daemon: Remove daemon datastructure dump functionality ... When sending SIGUSR1 to the daemon, it can crash because of a concurrent map access panic, showing a stack trace involving dumpDaemon. It appears it's not possible to recover from a concurrent map access panic. Since it's important that SIGUSR1 not be a destructive operation, sadly the best course of action I can think of is to remove this functionality. Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>	2017-06-08 14:08:49 -07:00
John Howard	4c62b12636	Spew debugging ... Signed-off-by: John Howard <jhoward@microsoft.com>	2016-11-03 10:05:11 -07:00
Alexander Morozov	e5d36586ac	daemon: always dump stack to file ... Dumping to log is unusable in 90% of cases and inspecting file is much more convenient. Signed-off-by: Alexander Morozov <lk4d4@docker.com>	2016-11-02 11:22:43 -07:00
John Howard	b63c92bf24	Windows: Stack dump to file ... Signed-off-by: John Howard <jhoward@microsoft.com>	2016-07-21 20:04:47 -07:00
John Howard	f4b08c7f5e	Windows: Win32 event for sigusr1 linux equivalence ... Signed-off-by: John Howard <jhoward@microsoft.com>	2015-07-06 18:58:53 -07:00

Renamed from daemon/debugtrap.go (Browse further)