On Wed, 18 Jun 2003, Igor Pechtchanski wrote:
> That's the way Windows debugging works -- once you attach to a process,
> detaching from it kills the process. No way around it.
I don't think this is true any more. XP enables debuggers (or at least the
VS debugger) to detach from executing pro
On Thu, 19 Jun 2003, Christopher Faylor wrote:
> On Wed, Jun 18, 2003 at 07:33:38PM -0400, Igor Pechtchanski wrote:
> >On 18 Jun 2003, Sam Steingold wrote:
> >>run a process in a cygwin window, find out its PID, run gdb in another
> >>window, attach to that process, then detach from it. the targe
On Wed, Jun 18, 2003 at 07:33:38PM -0400, Igor Pechtchanski wrote:
>On 18 Jun 2003, Sam Steingold wrote:
>>run a process in a cygwin window, find out its PID, run gdb in another
>>window, attach to that process, then detach from it. the target
>>process stops responding as soon as it is attached t
On Wed, Jun 18, 2003 at 07:33:38PM -0400, Igor Pechtchanski wrote:
> On 18 Jun 2003, Sam Steingold wrote:
>
> > run a process in a cygwin window, find out its PID, run gdb in another
> > window, attach to that process, then detach from it.
> > the target process stops responding as soon as it is a
On 18 Jun 2003, Sam Steingold wrote:
> run a process in a cygwin window, find out its PID, run gdb in another
> window, attach to that process, then detach from it.
> the target process stops responding as soon as it is attached to.
> detaching changes nothing.
> only after I exit gdb, I get the o
run a process in a cygwin window, find out its PID, run gdb in another
window, attach to that process, then detach from it.
the target process stops responding as soon as it is attached to.
detaching changes nothing.
only after I exit gdb, I get the original window responding, with the
terminal in
6 matches
Mail list logo
