This is the mail archive of the gdb@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]

Re: "run", and executable file/symtab association?

From: Randolph Chung <randolph at tausq dot org>
To: Daniel Jacobowitz <drow at false dot org>
Cc: msnyder at redhat dot com, gdb at sources dot redhat dot com
Date: Sun, 19 Feb 2006 01:28:13 +0800
Subject: Re: "run", and executable file/symtab association?
References: <dsu1q7$93m$1@sea.gmane.org> <20060215030909.GB8700@nevyn.them.org> <43F6EEB4.4040002@tausq.org> <20060218152827.GA21241@nevyn.them.org>

pop_target calls current_target->to_close.  I am suspecting that it
should call target_stack->to_close instead.

hrm, target_stack is "child", and its to_close method is NULL. target_stack->beneath is "exec" and its to_close is exec_close...

I don't pretend to understand this code and why if there are forks, we should be popping the target to kill everything.
I don't either.

ok, I'll wait for Michael to respond :)

randolph

Follow-Ups:
- Re: "run", and executable file/symtab association?
  - From: Daniel Jacobowitz

References:
- "run", and executable file/symtab association?
  - From: Randolph Chung
- Re: "run", and executable file/symtab association?
  - From: Daniel Jacobowitz
- Re: "run", and executable file/symtab association?
  - From: Randolph Chung
- Re: "run", and executable file/symtab association?
  - From: Daniel Jacobowitz

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