Oracle® Solaris Studio 12.4: Debugging a Program With dbx

Exit Print View

Updated: January 2015
 
 

Using Events

dbx provides events you can use with the stop, when, and trace commands on your OpenMP code. For information about using events with these commands, see Setting Event Specifications.

Synchronization Events

omp_barrier [type] [state]

Tracks the event of a thread entering a barrier.

type valid values are:

  • explicit – Track explicit barriers

  • implicit – Track implicit barriers

If you do not specify type, then only explicit barriers are tracked.

state valid values are:

  • enter – Report the event when any thread enters a barrier

  • exit – Report the event when any thread exits a barrier

  • all_entered – Report the event when all threads have entered a barrier

If you do not specify state, the default is all_entered.

If you specify enter or exit, you can include a thread ID to specify tracking only for that thread.

omp_taskwait [state]

Tracks the event of a thread entering a taskwait.

state valid values are:

  • enter – Report the event when a thread enters a taskwait

  • exit – Report the event when all child tasks have finished

If you do not specify state, then exit is the default.

omp_ordered [state]

Tracks the event of a thread entering an ordered region.

state valid values are:

  • begin – Report the event when an ordered region begins

  • enter – Report the event when a thread enters an ordered region

  • exit – Report the event when a thread exits an ordered region

If you do not specify state, then the default is enter.

omp_critical

Tracks the event of a thread entering a critical region.

omp_atomic [state]

Tracks the event of a thread entering an atomic region.

state valid values are:

  • begin – Report the event when an atomic region begins

  • exit – Report the event when a thread exits an atomic region

If you do not specify state, then the default is begin.

omp_flush

Tracks the event of a thread executing a flush.

Other Events

omp_task [state]

Tracks the creation and termination of tasks.

state valid values are:

  • create – Report the event when a task has just been created and before its execution begins

  • start – Report the event when a task starts its execution

  • finish – Report the event when a task has finished its execution and is about to be terminated

If you do not specify state, the default is start.

omp_master

Tracks the event of the master thread entering the master region.

omp_single

Tracks the event of a thread entering a single region.