Home
last modified time | relevance | path

Searched refs:debug_entry (Results 1 – 4 of 4) sorted by relevance

/linux/tools/perf/util/
H A Djitdump.h92 struct debug_entry { struct
104 struct debug_entry entries[]; argument
125 static inline struct debug_entry *
126 debug_entry_next(struct debug_entry *ent) in debug_entry_next()
134 debug_entry_file(struct debug_entry *ent) in debug_entry_file()
H A Dgenelf_debug.c300 static ubyte get_special_opcode(struct debug_entry *ent, in get_special_opcode()
335 struct debug_entry *ent, size_t nr_entry, in emit_lineno_info()
409 struct debug_entry *ent, size_t nr_entry, in add_debug_line()
479 struct debug_entry *ent = debug; in jit_process_debug_info()
/linux/tools/perf/Documentation/
H A Djitdump-specification.txt124 * debug_entry[n]: array of nr_entry debug entries for the function
126 The debug_entry describes the source line information. It is defined as follows in order:
132 The debug_entry entries are saved in sequence but given that they have variable sizes due to the file name string, they cannot be indexed directly.
133 They need to be walked sequentially. The next debug_entry is found at sizeof(debug_entry) + strlen(name) + 1.
/linux/tools/perf/jvmti/
H A Djvmti_agent.c455 size += nr_lines * sizeof(struct debug_entry); in jvmti_write_debug_info()