blob: f1ec78991c69c8f4c71915424084d5da3dbb06c1 [file] [log] [blame]
Petr Machata9294d822012-02-07 12:35:58 +01001/*
2 * This file is part of ltrace.
3 * Copyright (C) 2012 Petr Machata, Red Hat Inc.
4 * Copyright (C) 2009 Juan Cespedes
5 *
6 * This program is free software; you can redistribute it and/or
7 * modify it under the terms of the GNU General Public License as
8 * published by the Free Software Foundation; either version 2 of the
9 * License, or (at your option) any later version.
10 *
11 * This program is distributed in the hope that it will be useful, but
12 * WITHOUT ANY WARRANTY; without even the implied warranty of
13 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
14 * General Public License for more details.
15 *
16 * You should have received a copy of the GNU General Public License
17 * along with this program; if not, write to the Free Software
18 * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
19 * 02110-1301 USA
20 */
21
22#ifndef BREAKPOINT_H
23#define BREAKPOINT_H
24
25/* XXX This is currently a very weak abstraction. We would like to
26 * much expand this to allow things like breakpoints on SDT probes and
27 * such.
28 *
29 * In particular, we would like to add a tracepoint abstraction.
30 * Tracepoint is a traceable feature--e.g. an exact address, a DWARF
31 * symbol, an ELF symbol, a PLT entry, or an SDT probe. Tracepoints
32 * are named and the user can configure which of them he wants to
33 * enable. Realized tracepoints enable breakpoints, which are a
34 * low-level realization of high-level tracepoint.
35 *
36 * Tracepoints are provided by the main binary as well as by any
37 * opened libraries: every time an ELF file is mapped into the address
38 * space, a new set of tracepoints is extracted, and filtered
39 * according to user settings. Those tracepoints that are left are
40 * then realized, and the tracing starts.
41 *
42 * A scheme like this would take care of gradually introducing
43 * breakpoints when the library is mapped, and therefore ready, and
44 * would avoid certain hacks. For example on PPC64, we don't actually
45 * add breakpoints to PLT. Instead, we read the PLT (which contains
46 * addresses, not code), to figure out where to put the breakpoints.
47 * In prelinked code, that address is non-zero, and points to an
48 * address that's not yet mapped. ptrace then fails when we try to
49 * add the breakpoint.
50 *
51 * Ideally, return breakpoints would be just a special kind of
52 * tracepoint that has attached some magic. Or a feature of a
53 * tracepoint. Service breakpoints like the handling of dlopen would
54 * be a low-level breakpoint, likely without tracepoint attached.
55 *
56 * So that's for sometimes.
57 */
58
Petr Machatad3dc17b2012-03-21 03:23:25 +010059#include "sysdep.h"
Petr Machata2b46cfc2012-02-18 11:17:29 +010060#include "library.h"
Petr Machata9294d822012-02-07 12:35:58 +010061
62struct Process;
Petr Machataa9fd8f42012-02-07 13:25:56 +010063struct breakpoint;
64
65struct bp_callbacks {
66 void (*on_hit) (struct breakpoint *bp, struct Process *proc);
67 void (*on_destroy) (struct breakpoint *bp);
68};
Petr Machata9294d822012-02-07 12:35:58 +010069
Petr Machata9294d822012-02-07 12:35:58 +010070struct breakpoint {
Petr Machataa9fd8f42012-02-07 13:25:56 +010071 struct bp_callbacks *cbs;
Petr Machata29add4f2012-02-18 16:38:05 +010072 struct library_symbol *libsym;
Petr Machata9294d822012-02-07 12:35:58 +010073 void *addr;
74 unsigned char orig_value[BREAKPOINT_LENGTH];
75 int enabled;
Petr Machata2b46cfc2012-02-18 11:17:29 +010076 struct arch_breakpoint_data arch;
Petr Machata9294d822012-02-07 12:35:58 +010077};
78
Petr Machataa9fd8f42012-02-07 13:25:56 +010079/* Call on-hit handler of BP, if any is set. */
80void breakpoint_on_hit(struct breakpoint *bp, struct Process *proc);
81
Petr Machata2b46cfc2012-02-18 11:17:29 +010082/* Initialize a breakpoint structure. That doesn't actually realize
83 * the breakpoint. The breakpoint is initially assumed to be
84 * disabled. orig_value has to be set separately. CBS may be
85 * NULL. */
86int breakpoint_init(struct breakpoint *bp, struct Process *proc,
87 target_address_t addr, struct library_symbol *libsym,
88 struct bp_callbacks *cbs);
89
Petr Machata8cce1192012-03-25 01:37:19 +010090/* XXX this is currently not called anywhere. */
91void breakpoint_destroy(struct breakpoint *bp);
92
Petr Machata9294d822012-02-07 12:35:58 +010093/* This is actually three functions rolled in one:
94 * - breakpoint_init
Petr Machata8cce1192012-03-25 01:37:19 +010095 * - proc_breakpoint_insert
Petr Machata9294d822012-02-07 12:35:58 +010096 * - breakpoint_enable
97 * XXX I think it should be broken up somehow. */
98struct breakpoint *insert_breakpoint(struct Process *proc, void *addr,
99 struct library_symbol *libsym, int enable);
100
Petr Machatae9aebd62012-03-25 01:38:53 +0100101/* Name of a symbol associated with BP. May be NULL. */
102const char *breakpoint_name(const struct breakpoint *bp);
103
Petr Machata8cce1192012-03-25 01:37:19 +0100104/* Again, this seems to be several interfaces rolled into one:
105 * - breakpoint_disable
106 * - proc_breakpoint_remove
107 * - breakpoint_destroy
108 * XXX */
Petr Machata9294d822012-02-07 12:35:58 +0100109void delete_breakpoint(struct Process *proc, void *addr);
110
111/* XXX some of the following belongs to proc.h/proc.c. */
112struct breakpoint *address2bpstruct(struct Process *proc, void *addr);
113void enable_all_breakpoints(struct Process *proc);
114void disable_all_breakpoints(struct Process *proc);
115int breakpoints_init(struct Process *proc, int enable);
116
Petr Machata9294d822012-02-07 12:35:58 +0100117#endif /* BREAKPOINT_H */