* GDB/MI lawyer for Thread Creation
@ 2003-05-06 21:31 Alain Magloire
2003-05-06 21:51 ` Andrew Cagney
0 siblings, 1 reply; 6+ messages in thread
From: Alain Magloire @ 2003-05-06 21:31 UTC (permalink / raw)
To: gdb
Bonjour
Need a MI protocol guru for this. When threads are created gdb is sending
gdb -i mi
~"[NEW Thread 1024 (LWP 8288)]\n"
Useless for MI, how about a new OOB ?
*thread,thread-id="8288"
or a new async-notify ?
=thread,thread-id="8288"
Only "*stopped" is currently define as a possible oob.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: GDB/MI lawyer for Thread Creation
2003-05-06 21:31 GDB/MI lawyer for Thread Creation Alain Magloire
@ 2003-05-06 21:51 ` Andrew Cagney
2003-05-07 15:19 ` Event notification (was Re: GDB/MI lawyer for Thread Creation) Alain Magloire
0 siblings, 1 reply; 6+ messages in thread
From: Andrew Cagney @ 2003-05-06 21:51 UTC (permalink / raw)
To: Alain Magloire; +Cc: gdb
> Bonjour
>
> Need a MI protocol guru for this. When threads are created gdb is sending
>
> gdb -i mi
> ~"[NEW Thread 1024 (LWP 8288)]\n"
>
>
> Useless for MI, how about a new OOB ?
>
> *thread,thread-id="8288"
>
>
> or a new async-notify ?
>
> =thread,thread-id="8288"
>
> Only "*stopped" is currently define as a possible oob.
BTW, co/build kseitz_interps-20020528-branch, it also generates
breakpoint notify events.
I think that notify is correct (although it could be argued that exec is
a legetimate class (the difference is a bit arbitrary).
Andrew
^ permalink raw reply [flat|nested] 6+ messages in thread
* Event notification (was Re: GDB/MI lawyer for Thread Creation)
2003-05-06 21:51 ` Andrew Cagney
@ 2003-05-07 15:19 ` Alain Magloire
2003-05-07 16:16 ` Andrew Cagney
0 siblings, 1 reply; 6+ messages in thread
From: Alain Magloire @ 2003-05-07 15:19 UTC (permalink / raw)
To: gdb
>
> > Bonjour
> >
> > Need a MI protocol guru for this. When threads are created gdb is sending
> >
> > gdb -i mi
> > ~"[NEW Thread 1024 (LWP 8288)]\n"
> >
> >
> > Useless for MI, how about a new OOB ?
> >
> > *thread,thread-id="8288"
> >
> >
> > or a new async-notify ?
> >
> > =thread,thread-id="8288"
> >
> > Only "*stopped" is currently define as a possible oob.
>
> BTW, co/build kseitz_interps-20020528-branch, it also generates
> breakpoint notify events.
>
> I think that notify is correct (although it could be argued that exec is
> a legetimate class (the difference is a bit arbitrary).
>
I went digging in the old email exchanges with kseitz ....
And yes this is what I'm looking for
one nitpicking:
- the event notifications mechanism seem to be for side effects, for example
setting a breakpoint via CLI, notification is sent informing of the side effect.
Or assigning statements having side effects.
It does not seem to address "pure" async event. Threads creation/destruction,
and loading of shared libs are two examples that spring to mind about the need
of notification when the inferior is still running.
It those cases, I would say that sending an OOB instead of async-notify is more
appropriate.
Questions:
Will kseitz_interps-20020528-branch be merge to the main trunk?
Any ETA ?
I'm exited about this, it brings be closer in providing a more powerfull/flexible
gui debugger.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Event notification (was Re: GDB/MI lawyer for Thread Creation)
2003-05-07 15:19 ` Event notification (was Re: GDB/MI lawyer for Thread Creation) Alain Magloire
@ 2003-05-07 16:16 ` Andrew Cagney
2003-05-07 18:56 ` Alain Magloire
0 siblings, 1 reply; 6+ messages in thread
From: Andrew Cagney @ 2003-05-07 16:16 UTC (permalink / raw)
To: Alain Magloire; +Cc: gdb
> I went digging in the old email exchanges with kseitz ....
> And yes this is what I'm looking for
>
> one nitpicking:
>
> - the event notifications mechanism seem to be for side effects, for example
> setting a breakpoint via CLI, notification is sent informing of the side effect.
> Or assigning statements having side effects.
>
> It does not seem to address "pure" async event. Threads creation/destruction,
> and loading of shared libs are two examples that spring to mind about the need
> of notification when the inferior is still running.
>
> It those cases, I would say that sending an OOB instead of async-notify is more
> appropriate.
Hmm, makes sense - a real rationale. Anyone else have comments?
Want to re-word the MI doco so this is clearer?
> Questions:
> Will kseitz_interps-20020528-branch be merge to the main trunk?
> Any ETA ?
The branch contains a lot of stuff, but importantly prototypes for two
new features:
- interps command
- breakpoint events
The interps feature is now implemented in the mainline. The breakpoint
stuff has't been done. One missing bit of the framework needed for
that feature - observer.[hc] - was recently added by Joel though.
> I'm exited about this, it brings be closer in providing a more powerfull/flexible
> gui debugger.
Andrew
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Event notification (was Re: GDB/MI lawyer for Thread Creation)
2003-05-07 16:16 ` Andrew Cagney
@ 2003-05-07 18:56 ` Alain Magloire
2003-05-16 3:14 ` Andrew Cagney
0 siblings, 1 reply; 6+ messages in thread
From: Alain Magloire @ 2003-05-07 18:56 UTC (permalink / raw)
To: gdb
>
>
> > I went digging in the old email exchanges with kseitz ....
> > And yes this is what I'm looking for
> >
> > one nitpicking:
> >
> > - the event notifications mechanism seem to be for side effects, for example
> > setting a breakpoint via CLI, notification is sent informing of the side effect.
> > Or assigning statements having side effects.
> >
> > It does not seem to address "pure" async event. Threads creation/destruction,
> > and loading of shared libs are two examples that spring to mind about the need
> > of notification when the inferior is still running.
> >
> > It those cases, I would say that sending an OOB instead of async-notify is more
> > appropriate.
>
> Hmm, makes sense - a real rationale. Anyone else have comments?
>
> Want to re-word the MI doco so this is clearer?
>
heu .... being native french speaking... mais bien sure!!!
(evil laughter here ...)
> > Questions:
> > Will kseitz_interps-20020528-branch be merge to the main trunk?
> > Any ETA ?
>
> The branch contains a lot of stuff, but importantly prototypes for two
> new features:
> - interps command
> - breakpoint events
> The interps feature is now implemented in the mainline. The breakpoint
> stuff has't been done. One missing bit of the framework needed for
> that feature - observer.[hc] - was recently added by Joel though.
>
Observers ... looking trough the code ......
Was the observer pattern also intended for other notifications then stop.
Like
observer_attach_thread_creation()
observer_attach_shared_loaded()
etc ...
Or it is the wrong approach?
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Event notification (was Re: GDB/MI lawyer for Thread Creation)
2003-05-07 18:56 ` Alain Magloire
@ 2003-05-16 3:14 ` Andrew Cagney
0 siblings, 0 replies; 6+ messages in thread
From: Andrew Cagney @ 2003-05-16 3:14 UTC (permalink / raw)
To: Alain Magloire; +Cc: gdb
> heu .... being native french speaking... mais bien sure!!!
> (evil laughter here ...)
Your English can't be worse than my American.
>> > Questions:
>> > Will kseitz_interps-20020528-branch be merge to the main trunk?
>> > Any ETA ?
>
>>
>> The branch contains a lot of stuff, but importantly prototypes for two
>> new features:
>> - interps command
>> - breakpoint events
>> The interps feature is now implemented in the mainline. The breakpoint
>> stuff has't been done. One missing bit of the framework needed for
>> that feature - observer.[hc] - was recently added by Joel though.
>>
>
>
> Observers ... looking trough the code ......
> Was the observer pattern also intended for other notifications then stop.
> Like
> observer_attach_thread_creation()
> observer_attach_shared_loaded()
>
> etc ...
Yes, that's the intent. Finally a single notification mechanism.
The other bit is a script to convert gdb/doc/observer.texi into
gdb/observer.[hc].
Andrew
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2003-05-16 3:14 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-05-06 21:31 GDB/MI lawyer for Thread Creation Alain Magloire
2003-05-06 21:51 ` Andrew Cagney
2003-05-07 15:19 ` Event notification (was Re: GDB/MI lawyer for Thread Creation) Alain Magloire
2003-05-07 16:16 ` Andrew Cagney
2003-05-07 18:56 ` Alain Magloire
2003-05-16 3:14 ` Andrew Cagney
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).