Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joachim Protze <joachim.protze@tu-dresden.de>
To: gdb@sourceware.org
Subject: Re: GDB Talks at the GNU Cauldron
Date: Thu, 09 Feb 2012 08:18:00 -0000	[thread overview]
Message-ID: <4F338138.4030401@tu-dresden.de> (raw)
In-Reply-To: <4F32DAC8.8020408@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]

On 08.02.2012 21:27, Phil Muldoon wrote:
> According to the organizers there are three to four talks at the
> Cauldron.  Something that Diego mentioned was the need to coordinate
> talks.  So, who has submitted abstracts, and what are their titles? 
> It would be good to plan for this.
>
> Cheers,
>
> Phil

Titel: GDB vs. MPI (Message Passing Interface) -- Prepared presentation and 
demo

Authors: Joachim Protze & Andreas Knüpfer


Andreas will present the status of our work on making GDB more verbose in
context of MPI and MPI internal structures. The presentation will also give 
an overview to the possibilities, the MPI standard holds for debuggers and
other tools.

The work founds on the python api of GDB. Is there any need, to have some
declaring words on this api or should the presentation focus on the 
challenges when dealing with MPI?

Thanks
Joachim

-- 
Dipl.-Inf. Joachim Protze
Technische Universitaet Dresden
Center for Information Services and High Performance Computing (ZIH)



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5306 bytes --]

  parent reply	other threads:[~2012-02-09  8:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08 20:28 Phil Muldoon
2012-02-08 21:03 ` Kevin Pouget
2012-02-08 22:39 ` Stan Shebs
2012-02-09  8:18 ` Joachim Protze [this message]
2012-02-09 14:03 ` Jan Kratochvil

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F338138.4030401@tu-dresden.de \
    --to=joachim.protze@tu-dresden.de \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox