Simon Marchi 73ede76585 Constify thread name return path ...

Since this code path returns a string owned by the target (we don't know how
it's allocated, could be a static read-only string), it's safer if we return
a constant string.  If, for some reasons, the caller wishes to modify the
string, it should make itself a copy.

gdb/ChangeLog:

	* linux-nat.c (linux_nat_thread_name): Constify return value.
	* target.h (struct target_ops) <to_thread_name>: Likewise.
	(target_thread_name): Likewise.
	* target.c (target_thread_name): Likewise.
	* target-delegates.c (debug_thread_name): Regenerate.
	* python/py-infthread.c (thpy_get_name): Constify local variables.
	* thread.c (print_thread_info): Likewise.
	(thread_find_command): Likewise.

2015-11-26 09:49:03 -05:00

..

lib/gdb

…

py-arch.c

…

py-auto-load.c

…

py-block.c

…

py-bpevent.c

…

py-breakpoint.c

…

py-cmd.c

…

py-continueevent.c

…

py-event.c

…

py-event.h

…

py-events.h

…

py-evtregistry.c

…

py-evts.c

…

py-exitedevent.c

…

py-finishbreakpoint.c

…

py-frame.c

…

py-framefilter.c

Don't assume break/continue inside a TRY block works

2015-10-29 12:55:01 +00:00

py-function.c

…

py-gdb-readline.c

…

py-inferior.c

Change some void* to gdb_byte*

2015-10-09 10:08:23 -04:00

py-infevents.c

…

py-infthread.c

Constify thread name return path

2015-11-26 09:49:03 -05:00

py-lazy-string.c

…

py-linetable.c

…

py-newobjfileevent.c

…

py-objfile.c

…

py-param.c

…

py-prettyprint.c

…

py-progspace.c

…

py-signalevent.c

…

py-stopevent.c

…

py-stopevent.h

…

py-symbol.c

…

py-symtab.c

…

py-threadevent.c

…

py-type.c

Fix accessing a function's fields (parameters) from Python (PR 18073)

2015-10-21 15:57:22 -04:00

py-unwind.c

…

py-utils.c

…

py-value.c

Don't assume break/continue inside a TRY block works

2015-10-29 12:55:01 +00:00

py-varobj.c

…

py-xmethods.c

…

python-config.py

…

python-internal.h

…

python.c

Add cast in python.c

2015-10-22 12:13:19 -04:00

python.h

…