8 commits

Author	SHA1	Message	Date
Michael Eischer	d768c1c3e4	Allow cleanup handlers to filter the exit code	2022-08-26 23:04:59 +02:00
Michael Eischer	c60540b196	add go:build headers everywhere	2022-03-28 22:23:47 +02:00
Alexander Neumann	d926b9fd80	Add profile build flag	2018-04-30 14:19:04 +02:00
Alexander Neumann	4ba8d40282	Add block profile option	2018-04-30 14:18:45 +02:00
Alexander Neumann	09365cc4ea	Add --trace-profile	2018-04-22 11:37:05 +02:00
Michael Pratt	e4c469c149	debug: properly handle interrupted profiles ... By default (i.e., without profile.NoShutdownHook), profile.Start listens for SIGINT and will stop the profile and call os.Exit(0). restic already listens for SIGINT and runs its own cleanup handlers before calling os.Exit(0). As is, these handlers are racing when an interrupt occurs, and in my experience, restic tends to win the race, resulting in an unusable profile. Eliminate the race and properly stop profiles on interrupt by disabling package profile's signal handler and instead stop the profile in a restic cleanup handler.	2017-08-28 22:03:26 -07:00
Alexander Neumann	6caeff2408	Run goimports	2017-07-23 14:21:03 +02:00
Alexander Neumann	83d1a46526	Moves files	2017-07-23 14:19:13 +02:00

Renamed from src/cmds/restic/global_debug.go (Browse further)