This is the mail archive of the gdb-patches@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: [RFA] Report the main thread.


 > There has been a discussion earlier about the merits and drawbacks
 > of adding the main "thread" to the list of threads when debugging
 > an application that doesn't use threads.  We only considered the
 > perspective of the user, but there is indeed the case of front-ends.
 > Assuming that the decision still stands, I think it is reasonable
 > to ask the front-ends to check that there is more than one thread
 > before going into "thread" mode.  I understand that this is making
 > things a little more complicated, but it shouldn't be that hard.
 > 
 > On the other hand, if there is a way to detect that the new "thread"
 > is from an unthreaded program, we could decide to not emit the
 > notification. But I would like things to be consistent - it should
 > be the same for both CLI, MI and annotations.

CLI and MI are both interpreters.  Annotations are just a markup of CLI
output, so I don't think they should be considered equally.

I don't see the need to report the main thread but if Pedro and Vladimir do,
then I'm happy to live with that.  If I propose an annotation that doesn't
report the main thread, then since they won't be using it, I would expect that
they won't object.  Furthermore, since annotations would never be used with MI
and they are destined for removal anyway, trying to make them consistent seems
a pointless exercise.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


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