This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[PATCH] Fix error when gdb connect to a stub that tracepoint is running[2/2] add inserted to create_breakpoint


Hi,

If we got a tracepoint from gdbstub part, we will create it.
If the tracepoint is running and the gdbstub support tracepoint running insert, create_breakpoint will insert this tracepoint that get from gdbstub to gdbstub.
This is an issue.
So this patch add a flags to create_breakpoint to let this function know that this breakpoint already inserted.


2012-01-31 Hui Zhu <hui_zhu@mentor.com>

	* breakpoint.h (CREATE_BREAKPOINT_FLAGS_INSERTED): New macro.
	(create_breakpoint): Add new argument flags.
	* breakpoint.c (create_breakpoint): Add new argument flags.
	if flags include CREATE_BREAKPOINT_FLAGS_INSERTED, set breakpoint
	to inserted.
	(handle_gnu_v3_exceptions): Add new argument flags to
	function create_breakpoint.
	(trace_command): Ditto.
	(ftrace_command): Ditto.
	(strace_command): Ditto.
	(create_tracepoint_from_upload): Ditto.
	* mi/mi-cmd-break.c (mi_cmd_break_insert): Ditto.
	* python/py-breakpoint.c (bppy_init): Ditto.
	* python/py-finishbreakpoint.c (bpfinishpy_init): Ditto.
	* spu-tdep.c (spu_catch_start): Ditto.

Thanks,
Hui

Attachment: create_breakpoint-inserted.txt
Description: Text document


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]