Bug 106238 - gdb attachment for parallel runs
Summary: gdb attachment for parallel runs
Status: RESOLVED INTENTIONAL
Alias: None
Product: valgrind
Classification: Developer tools
Component: memcheck (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR wishlist
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-24 23:46 UTC by Jeff Keasler
Modified: 2014-12-14 21:30 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff Keasler 2005-05-24 23:46:02 UTC
Hi,

I'm using valgrind on a two processor MPI run using shmem, and it seems to be
working great.  I want to attach the gdb debugger but when I try to do so, the
underlying processes appear to be competing for stdin.  It would be nice to
attach the debugger to only one of the underlying processes, or better yet, to
be able to pop up a new window for each debugger attached.  The hard way to do
this would involve using sockets, but I'm hoping there may be a quick way using
a clean but limited hack.
Comment 1 Tom Hughes 2005-07-18 15:20:28 UTC
How about writing a shell script that does 'exec xterm -e gdb "$@"' and then telling valgrind to use that script as the debugger?
Comment 2 Florian Krohm 2014-12-14 21:30:48 UTC
--db-attach is deprecated as of release 3.10.