Re: [PATCH 04/10] Remove support for thread events without TRACE_EVENT_CLONE in GDBServer.

Yao Qi
2015-11-03T17:05:07Z

Antoine Tremblay <antoine.tremblay@ericsson.com> writes:

Hi,
I don't have objection to this direction...

> gdb/gdbserver/ChangeLog:
>
> * linux-low.c (linux_look_up_symbols): Don't call
> linux_supports_traceclone.
> * linux-low.h (thread_db_init): Remove use_events argument.
> * thread-db.c (thread_db_use_event): Remove global variable.
> (struct thread_db) <td_thr_event_enable_ftype>: Remove field.

s/td_thr_event_enable_ftype/td_thr_event_enable_p

We can also remove td_create_bp field.

> (thread_db_create_event): Remove function.
> (thread_db_enable_reporting): Likewise.

We can also remove remove_thread_event_breakpoints.

> (find_one_thread): Don't check for thread_db_use_events.
> (attach_thread): Likewise.
> (thread_db_load_search): Remove td_thr_event_enable_p initialization.
> (try_thread_db_load_1): Don't check for thread_db_use_events.
> (thread_db_init): Remove use_events argument.
> (thread_db_init): Remove thread events handling.

You mention function thread_db_init twice.

--
Yao (齐尧)