Re: [cdt-debug-dev] Execution lost in pthread while debuggingwithCygwin

[John Cortell <john.cortell@xxxxxxxxxxxxx>]

Mikhail's point here is that you need to think of Eclipse as a 
front-end to gdb, much list ddd is. If you debug your program in gdb 
and the same behavior occurs, it's either a problem in your program 
or in gdb or something else, but it won't be an Eclipse problem.

If you don't see the problem when debugging your app in gdb, then you 
have a pretty good case for it being an Eclipse issue. From the sound 
of it, though, I don't think that's going to be the case.

John

At 11:11 AM 4/6/2006, you wrote:
> Mikhail,
> If there was a problem with the program exe shouldn't it also happen 
> when it is executed from the command line or with a Windows double 
> click i.e. without any debugger being in the picture. However that 
> is not the case - the program runs fine when executed without the debugger.
> I will check the gdb trace.
>
> Thanks,
> Sudhan
>
> > From: "Mikhail Khodjaiants" <mikhailk@xxxxxxx>
> > Reply-To: CDT Debug developers list <cdt-debug-dev@xxxxxxxxxxx>
> > To: "CDT Debug developers list" <cdt-debug-dev@xxxxxxxxxxx>
> > Subject: Re: [cdt-debug-dev] Execution lost in pthread while 
> > debuggingwithCygwin GDB
> > Date: Thu, 6 Apr 2006 11:50:56 -0400
> >
> > Sudhan,
> >
> > Try to reproduce the same sequence from the command line or get the 
> > gdb trace (see CDT Debugger FAQ #5). I don't see anything wrong 
> > with the CDT debugger, it seems that your program is blocked.
> >
> > Mikhail
> > ----- Original Message ----- From: "Sudhan Kayarkar" <sudhank@xxxxxxxxxxx>
> > To: <cdt-debug-dev@xxxxxxxxxxx>
> > Sent: Thursday, April 06, 2006 11:33 AM
> > Subject: Re: [cdt-debug-dev] Execution lost in pthread while 
> > debugging withCygwin GDB
> >
> >
> > > Mikhail ,
> > >
> > > What I mean is that I can step through the code until it reaches here -
> > >
> > > pthread_mutexattr_t attr;
> > >
> > > => pthread_mutexattr_init(&attr);
> > >
> > > At the line where the pthread_mutexattr_init routine is called, if I do
> > > a
> > > Step Over or Step Into or Run (with a breakpoint on the next line) the
> > > debugger doesn't return and the execution just seems to get lost. The
> > > only
> > > thing I can do is suspend or terminate. The Debug window shows 2 threads
> > > -
> > > the status of this one is 'Stepping' and the status of the other is
> > > 'Running'.
> > >
> > > The error log does not generate any message when this happens.
> > >
> > > Thanks,
> > > Sudhan
> > >
> > >
> > > > From: "Mikhail Khodjaiants" <mikhailk@xxxxxxx>
> > > > Reply-To: CDT Debug developers list <cdt-debug-dev@xxxxxxxxxxx>
> > > > To: "CDT Debug developers list" <cdt-debug-dev@xxxxxxxxxxx>
> > > > Subject: Re: [cdt-debug-dev] Execution lost in pthread while debugging
> > > > withCygwin GDB Date: Wed, 5 Apr 2006 17:27:45 -0400
> > > >
> > > > What do you mean by "control does not return to the debugger"? Is the
> > > > session in the running state? Check the error log.
> > > >
> > > > ----- Original Message ----- From: "Sudhan Kayarkar"
> > > <sudhank@xxxxxxxxxxx>
> > > > To: <cdt-debug-dev@xxxxxxxxxxx>
> > > > Sent: Wednesday, April 05, 2006 5:06 PM
> > > > Subject: [cdt-debug-dev] Execution lost in pthread while debugging with
> > >
> > > > Cygwin GDB
> > > >
> > > >
> > > > > I have a multi threaded project executable built using g++ that runs
> > > > > fine
> > > > > from command line or Windows double click.
> > > > > However, when I try to debug using Cygwin GDB the execution gets lost
> > > > > when a
> > > > > call to pthread_mutexattr_init is made i.e. control does not return to
> > > > > the
> > > > > debugger.
> > > > >
> > > > > The point at which this happens is NOT the first time that this
> > > pthread
> > > > > function is invoked. There are earlier invocations of this function
> > > that
> > > > > execute fine.
> > > > >
> > > > > Any clues about what might be happening or how this issue can be root
> > > > > caused
> > > > > ?
> > > > > Thanks,
> > > > > Sudhan
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > cdt-debug-dev mailing list
> > > > > cdt-debug-dev@xxxxxxxxxxx
> > > > > https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
> > > >
> > > > _______________________________________________
> > > > cdt-debug-dev mailing list
> > > > cdt-debug-dev@xxxxxxxxxxx
> > > > https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
> > >
> > >
> > > _______________________________________________
> > > cdt-debug-dev mailing list
> > > cdt-debug-dev@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
> >
> > _______________________________________________
> > cdt-debug-dev mailing list
> > cdt-debug-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
>
>
> _______________________________________________
> cdt-debug-dev mailing list
> cdt-debug-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev