\section{OpenMP Runtime Interface}Cheers, John D.
\label{runtime-interface:sec}
As part of the OpenMP interface, OMPD requires that the OpenMP
runtime system provides a public variable \verb|ompd_dll_locations|,
which is an \texttt{argv}-style vector of filename string pointers that
provides the pathnames(s) of any compatible OMPD plugin
implementations (if any).
\texttt{ompd\_dll\_locations} must have \texttt{C} linkage.
The debugger uses the name verbatim, and in particular, will
not apply any name mangling befor performing the look up.
The pathnames may be relative or absolute.
\begin{quote}
\begin{lstlisting}
const char **ompd_dll_locations;
\end{lstlisting}
\end{quote}
\labeldef{dll-locations:def}
\noindent
%%%% The value of \verb|ompd_dll_locations| may be NULL initially,
%%%% but must be filled in before \verb|ompd_initialize| is called.
%%%% After that,
\verb|ompd_dll_locations| shall point to a NULL-terminated
vector of zero or more NULL-terminated pathname strings.
There are no filename conventions for pathname strings.
The last entry in the vector shall be NULL.
The vector of string pointers must be fully initialized \emph{before}
\texttt{ompd\_dll\_locations} is set to a non-NULL value,
such that if the debugger stops execution at any point
where \texttt{ompd\_dll\_locations} is non-NULL, then the vector
of strings it points to is valid and complete.
The programming model or architecture of the debugger (and hence
that of the required OMPD) might not match that of the target
OpenMP program.
It is the responsibility of the debugger to interpret the contents
of \texttt{ompd\_dll\_locations} to find a suitable OMPD that matches
its own architectural characteristics.
On platforms that support different programming models
(\textit{e.g.}, 32 v. 64-bit), OpenMP implementers are encouraged
to provide OMPD implementations for all models, and which can handle
targets of any model.
Thus, for example, a 32-bit debugger should be able to debug a 64-bit target
by loading a 32-bit OMPD that can manage a 64-bit OpenMP runtime.
The OpenMP runtime shall notify the debugger that
\texttt{ompd\_dll\_locations} is valid by calling:
\begin{quote}
\begin{lstlisting}
void ompd_dll_locations_valid ( void );
\end{lstlisting}
\end{quote}
\labeldef{dll-locations-valid:def}
\noindent
The debugger can receive notification of this event by planting
a breakpoint in this routine.
\texttt{ompd\_dll\_locations\_valid ()} has \texttt{C} linkage,
and the debugger will not apply name mangling before searching
for this routine.
Hi Jeff, Yes, that is a good idea. I am not sure when I will get around to actually moving all the content, so in the short term, I should at least put a pointer to the new page on the old one... Thanks! Kathryn _________________________________________________________________ Kathryn Mohror, kathryn@llnl.gov, http://scalability.llnl.gov/ Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA-----Original Message----- From: Jeff Squyres (jsquyres) [mailto:jsquyres@cisco.com] Sent: Wednesday, August 12, 2015 7:56 AM To: kathryn@llnl.gov; MPI Tool WG Subject: Re: [mpiwg-tools] Meeting reminder: Thursday, 8/13 Kathryn -- If you didn't do so already, might I suggest that you remove the contentsofthe old wiki page and simply leave a pointer to the new one?On Aug 12, 2015, at 10:44 AM, Kathryn Mohror <kathryn@llnl.gov> wrote: Hi everyone, This is a reminder of our regular tools WG telecon this Thursday at 8:00 AM PDT, 11:00 EDT. You can access the webex information from thewiki:https://bitbucket.org/mpiforum/toolswg/wiki/Meetings Note that the wiki page has moved! The old content remains on the older wiki, but we are moving to a bitbucket. I am slowly transitioning content over, and plan to put new content only on the new wiki. Please let me know if you have any trouble accessing the newwiki site:https://bitbucket.org/mpiforum/toolswg/wiki/Home Agenda: QMPI - ~1st half hour Debugger topics - ~2nd half hour Talk to you soon! Kathryn__________________________________________________________ _______Kathryn Mohror, kathryn@llnl.gov, http://scalability.llnl.gov/ Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA _______________________________________________ mpiwg-tools mailing list mpiwg-tools@lists.mpi-forum.org http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools-- Jeff Squyres jsquyres@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/_______________________________________________ mpiwg-tools mailing list mpiwg-tools@lists.mpi-forum.org http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools