Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] Doubt related to terminate action event 
The workflow of terminate() is simple. If gdb is running it interrupts it and then calls "kill" command to gdb. Implementation of interrupt is platform-specific.

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Nayna Jain
Sent: Thursday, December 03, 2009 6:57 PM
To: CDT General developers list.
Subject: RE: [cdt-dev] Doubt related to terminate action event

I tried debugging.. It is actually calling MISession.getMIInferior().terminate().

That means it is calling terminate() of MIInferior class.

In that it is not satisfying either if or else condition and thus doesn't do anything.

The comment in the function MIInferior.terminate() method is not very clear.

Can you explain what does it tries to do there ? And how can I make
terminate() work.

>From the debug view I had given the terminate on the configuration name
i.e. New_Configuration(3) I selected and then clicked on terminate.

Thanks & Regardsm
Nayna Jain



             "Mikhail
             Khodjaiants"
             <Mikhail.Khodjaia                                          To
             nts@xxxxxxx>              "CDT General developers list."
             Sent by:                  <cdt-dev@xxxxxxxxxxx>
             cdt-dev-bounces@e                                          cc
             clipse.org
                                                                   Subject
                                       RE: [cdt-dev] Doubt related to
             12/03/2009 10:49          terminate action event
             PM


             Please respond to
               "CDT General
             developers list."
             <cdt-dev@eclipse.
                   org>






The terminate action is applied to the current selection in the debug view and the result may be different. But it seems that in this case
MIInferiour.terminate() is called regardless of what is selected.

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Nayna Jain
Sent: Thursday, December 03, 2009 4:27 PM
To: CDT General developers list.
Subject: RE: [cdt-dev] Doubt related to terminate action event

I tried doing that but this terminate method is not getting called.

And sorry I didn't get the meaning of what I am trying to terminate.

Because I guess if I click on terminate action button in Debug View then it will terminate both the gdb session as well as the program being run.

Do I understand it right ?

Thanks & Regards,
Nayna Jain





             "Mikhail

             Khodjaiants"

             <Mikhail.Khodjaia
To
             nts@xxxxxxx>              "CDT General developers list."

             Sent by:                  <cdt-dev@xxxxxxxxxxx>

             cdt-dev-bounces@e
cc
             clipse.org


Subject
                                       RE: [cdt-dev] Doubt related to

             12/03/2009 09:51          terminate action event

             PM





             Please respond to

               "CDT General

             developers list."

             <cdt-dev@eclipse.

                   org>









Try to set a breakpoint in MISession.terminate() or
MIInferior.terminate() depending on what is you trying to terminate: gdb or the program you are debugging.

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Nayna Jain
Sent: Thursday, December 03, 2009 4:01 PM
To: CDT General developers list.
Subject: [cdt-dev] Doubt related to terminate action event

Thanks John and Mikhail for the response related to MIInferior class.

I have one more doubt.. Its related to registering the SessionManager for getting debug events.

I have return a new launch configuration. In my new delegate, after doing some of the steps required for my launch,

I am using the launch of LocalCDILaunchDelegate.
Now in this case, though the debug starts and stack frame is displayed but when I do terminate action on running debug process, the terminate is not happening. I tried putting breakpoints and then debugging the issue it seems that the SessionManager
handleTerminateEvents() or handleDebugEvents() are not getting called.

Since they are not getting called it seems the event is either not received or not handled.

Can someone tell what might be the issue and how to make sure that terminate event is received ?

Thanks & Regards,

Nayna Jain





             John Cortell

             <rat042@freescale

             .com>
To
             Sent by:                  "CDT General developers list."

             cdt-dev-bounces@e         <cdt-dev@xxxxxxxxxxx>, "CDT
General
             clipse.org                developers list."

                                       <cdt-dev@xxxxxxxxxxx>


cc
             12/03/2009 07:48

             PM
Subject
                                       RE: [cdt-dev] Purpose of MIInferior
                                       class

             Please respond to

               "CDT General

             developers list."

             <cdt-dev@eclipse.

                   org>









That's what I get for trying to quickly scan the code and come up with an answer. Thought I had it right, but oh welll...

John

At 08:16 AM 12/3/2009, Mikhail Khodjaiants wrote:
>John,
>
>It's the opposite, MIInferior represents the process being debugged.
>
>Mikhail
>-----Original Message-----
>From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
>On Behalf Of John Cortell
>Sent: Thursday, December 03, 2009 2:00 PM
>To: CDT General developers list.; cdt-dev@xxxxxxxxxxx
>Subject: Re: [cdt-dev] Purpose of MIInferior class
>
>Nayna,
>
>MIInferior is the java.lang.Process that represents the gdb process
>itself, as opposed to the, say, the "Hello World" process the user is
>debugging.
>
>You will see that the gdb process is represented in the Debug view.
>The model object associated with that view element is an MIInferior
>instance.
>
>As for standalone documentation on the gdb/mi CDI reference
>implementation, there is none that I know of.  Detailed low level
>documents is not something you're not going to come across very often
>in CDT, but I think that holds true for many projects. There are
>comments in the code, but admittedly, they are sparse. In a perfect
>world, committers would thoroughly document their
classes/interfaces/methods.
>Often, though, the focus is on developing good software that performs,
>is well designed, and intuitive. If software meets those three
>criteria, engineers can often learn the design simply by studying the
>code. It's not an ideal situation, but it's something.
>
>John
>
>At 05:20 AM 12/3/2009, Nayna Jain wrote:
> >Hi all,
> >
> >What is the purpose of MIInferior class in
>org.eclipse.cdt.debug.mi.core ?
> >
> >Is there any document which tells how the connection to gdb/mi is
> >mapped in our cdt debug model ?
> >
> >Which class represents what ?
> >
> >Thanks & Regards,
> >Nayna Jain
> >
> >_______________________________________________
> >cdt-dev mailing list
> >cdt-dev@xxxxxxxxxxx
> >https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>
>_______________________________________________
>cdt-dev mailing list
>cdt-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/cdt-dev
>--
>IMPORTANT NOTICE: The contents of this email and any attachments are
>confidential and may also be privileged. If you are not the intended
>recipient, please notify the sender immediately and do not disclose the

>contents to any other person, use it for any purpose, or store or copy
>the information in any medium.  Thank you.
>_______________________________________________
>cdt-dev mailing list
>cdt-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/cdt-dev


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
--
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
--
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.

Back to the top