From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fac41,2c8b175fe3f63b8c
X-Google-Attributes: gidfac41,public
X-Google-Thread: f4fd2,2c8b175fe3f63b8c
X-Google-Attributes: gidf4fd2,public
X-Google-Thread: 103376,2c8b175fe3f63b8c
X-Google-Attributes: gid103376,public
X-Google-Thread: 10dd18,2c8b175fe3f63b8c
X-Google-Attributes: gid10dd18,public
X-Google-Thread: 114809,2c8b175fe3f63b8c
X-Google-Attributes: gid114809,public
X-Google-Thread: 1111a3,2c8b175fe3f63b8c
X-Google-Attributes: gid1111a3,public
X-Google-Thread: 1008e3,2c8b175fe3f63b8c
X-Google-Attributes: gid1008e3,public
From: kilgallen@eisner.decus.org (Larry Kilgallen)
Subject: Re: Threading questions (for FAQ).
Date: 1996/09/18
Message-ID: <1996Sep18.075157.1@eisner>#1/1
X-Deja-AN: 181356388
x-nntp-posting-host: eisner.decus.org
references: <51m7kr$9cq@oclc.org> <323FA609.1654@netvision.net.il>
x-nntp-posting-user: KILGALLEN
x-trace: 843047522/16902
organization: LJK Software
newsgroups: 
 comp.lang.ada,comp.lang.eiffel,comp.lang.lisp,comp.lang.modula3,comp.lang.objective-c,comp.lang.python,comp.lang.smalltalk
Date: 1996-09-18T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <323FA609.1654@netvision.net.il>, Calius <tow@netvision.net.il> writes:
> Sean Walton wrote:
>> 
>> I am putting together a FAQ for Linux Threads, and I understand that this
>> language supports threading in some degree.  Could anyone please help me
>> answer the following questions:

>>         4. How do you debug threads within this language?
> 
> Depends on your debbuger and environment.  I know my debbuger (Verdix
> SELF for
> IBM RS6000, AIX) has to ability to set breakpoints at specific tasks,
> and I think
> that should be the case for any decent ADA debugger.

As another example of the debug situation for a specific environment,
the VMS Debugger offers the following elements specific to Ada, most
of which have to do with tasking (threads):

DBG> show event_facility
event facility is ADA

  The general forms of commands to set a breakpoint or tracepoint
  on an Ada event are:
    SET BREAK/EVENT=event [task[, ... ]] [WHEN(expr)] [DO(comnd[; ... ])]
    SET TRACE/EVENT=event [task[, ... ]] [WHEN(expr)] [DO(comnd[; ... ])]

  If tasks are specified, the breakpoint will trigger only if the
  event occurs for those specific tasks.

  Ada event names and their definitions

  ABORT_TERMINATED      a task is terminating because of abort
  ACTIVATING            a task is about to begin its activation
  DEPENDENTS_EXCEPTION  an exception is about to cause a task to await
                        dependent tasks
  EXCEPTION_TERMINATED  a task is terminating because of an exception
  HANDLED               an exception is about to be handled
  HANDLED_OTHERS        an exception is about to be handled in an OTHERS handler
  PREEMPTED             a task is about to be preempted
  RENDEZVOUS_EXCEPTION  an exception is propagating out of a rendezvous
  RUN                   a task is about to run
  SUSPENDED             a task is about to be suspended
  TERMINATED            a task is terminating (including by abort or exception)
DBG>

I think readers of comp.lang.ada would appreciate a one-time posting
of your completed FAQ when completed, so we can get a picture of how
the other half lives.

Larry Kilgallen