|
From: Uday R. <uda...@gm...> - 2012-11-06 15:12:23
|
On Tue, Nov 6, 2012 at 8:34 PM, John Reiser <jr...@bi...> wrote: >> With vgdb/gdb, the debugger hangs after a couple of continues. >> >> Program received signal SIGTRAP, Trace/breakpoint trap. >> 0x000000300b4ea3d7 in writev () from /lib64/libc.so.6 > > Is there a real 'int3' instruction there, or was SIGTRAP sent > from somewhere else [using kill()]? Look with something like: > (gdb) x/20i 0x000000300b4ea3d7 - 0x20 > > [Philippe, please comment.] > >> There is no progress after this. The CPU utilization is 0 and it looks >> like memcheck has hung. On the valgrind side, I see >> ==29118== Syscall param writev(vector[...]) points to uninitialised byte(s) >> ==29118== at 0x300B4EA3D7: writev (in /usr/lib64/libc-2.15.so) >> ==29118== by 0x6256B92: ??? (in >> /usr/lib64/openmpi/lib/openmpi/mca_oob_tcp.so) > > What are the likely parameters to that writev()? How many different pieces, > of what sizes, etc.? Would the output be going to a disk file, or to a socket? The output would be going to a socket. I believe it's just sending out a buffer. If it's just sending out uninitialized data, it should perhaps not be related to the "invalid read" that I see via valgrind at a later stage? Thanks. > > -- > > > ------------------------------------------------------------------------------ > LogMeIn Central: Instant, anywhere, Remote PC access and management. > Stay in control, update software, and manage PCs from one command center > Diagnose problems and improve visibility into emerging IT issues > Automate, monitor and manage. Do more in less time with Central > http://p.sf.net/sfu/logmein12331_d2d > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |