From e7deac3aad394325f9e6fc6fda41d34ec94a59e0 Mon Sep 17 00:00:00 2001 From: Alexey Neyman Date: Fri, 19 May 2017 21:58:46 -0700 Subject: Switch comp.libs/tools and debug to new framework. Signed-off-by: Alexey Neyman --- .../ltrace/0.7.3/006-unexpected-breakpoint.patch | 22 ---------------------- 1 file changed, 22 deletions(-) delete mode 100644 patches/ltrace/0.7.3/006-unexpected-breakpoint.patch (limited to 'patches/ltrace/0.7.3/006-unexpected-breakpoint.patch') diff --git a/patches/ltrace/0.7.3/006-unexpected-breakpoint.patch b/patches/ltrace/0.7.3/006-unexpected-breakpoint.patch deleted file mode 100644 index 443bee42..00000000 --- a/patches/ltrace/0.7.3/006-unexpected-breakpoint.patch +++ /dev/null @@ -1,22 +0,0 @@ -From: Juan Cespedes -Description: continue after unexpected breakpoint - (instead of decrementing PC and execute int3 again and again) -Last-Update: 2014-01-03 - - ---- ltrace-0.7.3.orig/handle_event.c -+++ ltrace-0.7.3/handle_event.c -@@ -656,9 +656,12 @@ handle_breakpoint(Event *event) - - if ((sbp = address2bpstruct(leader, brk_addr)) != NULL) - breakpoint_on_hit(sbp, event->proc); -- else if (event->proc->state != STATE_IGNORED) -+ else if (event->proc->state != STATE_IGNORED) { - output_line(event->proc, - "unexpected breakpoint at %p", brk_addr); -+ continue_process(event->proc->pid); -+ return; -+ } - - /* breakpoint_on_hit may delete its own breakpoint, so we have - * to look it up again. */ -- cgit v1.2.3