FreeChainXenon/binutils-gdb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

2011-12-20 Pedro Alves <alves.ped@gmail.com>

Browse source 
Jan Kratochvil  <jan.kratochvil@redhat.com>

        * linux-nat.c (add_lwp): Don't call linux_nat_new_thread on the
	first LWP.
	* amd64-linux-nat.c (update_debug_registers_callback): Instantiate
	`lwp->arch_private' if NULL.
	(amd64_linux_prepare_to_resume): Do nothing if `lwp->arch_private'
	is NULL.
	* i386-linux-nat.c (update_debug_registers_callback): Instantiate
	`lwp->arch_private' if NULL.
	(i386_linux_prepare_to_resume): Do nothing if `lwp->arch_private'
	is NULL.
This commit is contained in:
Pedro Alves 2011-12-20 10:40:15 +00:00
parent 87c31f0622
commit 6e012a6c38
4 changed files with 41 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

10
gdb/linux-nat.c
View file

@ -1151,7 +1151,15 @@ add_lwp (ptid_t ptid)
lp->next = lwp_list;
lwp_list = lp;
if (linux_nat_new_thread != NULL)
/* Let the arch specific bits know about this new thread. Current
clients of this callback take the opportunity to install
watchpoints in the new thread. Don't do this for the first
thread though. If we're spawning a child ("run"), the thread
executes the shell wrapper first, and we shouldn't touch it until
it execs the program we want to debug. For "attach", it'd be
okay to call the callback, but it's not necessary, because
watchpoints can't yet have been inserted into the inferior. */
if (num_lwps (GET_PID (ptid)) > 1 && linux_nat_new_thread != NULL)
linux_nat_new_thread (lp);
return lp;