[Dpcl-develop] bcreate - stdout and stdin callbacks

[Steve C. <sl...@sg...>]

     Greetings, everyone. The Open/SpeedShop project at SGI has come
  across a <perceived> problem with the ability to specify callbacks
  for 'stdout' and 'stderr' at the time of 'bcreating' a new mutatee.
  Despite our best efforts, it appears that both stdout and stderr
  are redirected to 'dpcl.nnn.stdout' and 'dpcl.nnn.stderr' files. What
  we <think> we would like to see if we specify ONLY callback functions
  in the mutator for both stderr and stdout, and we do NOT specify any
  remote filenames, is that the mutator will be fed stdout I/O from
  the mutatee into its specified function entry point (e.g. stdout_cb)
  and stderr I/O from the mutatee into its specified callback function
  in the mutator (e.g. stderr_cb). The code in ProcessD::create, however,
  only seems to 'pipe' things into existing <dpcld> fd's for stdout
  and stderr (i.e. the dpcl.nnn.stdout/stderr files). AFAICT there is
  not attempt to build messages to the mutator(client) consisting of
  the mutatee's stdout or stderr output, whichever is in play.
     Are we (SGI) misreading the capabilities of this 'bcreate'
  feature? It might very well be the case that the Hybrid changes
  foul things up because we have already seen one instance of that
  occurring with <dpcld> termination messages.
     Clues welcome. My clueless DPCL state continues......

                                         SteveC - SGI Compilers/Tools