|
From: Uday R. <uda...@gm...> - 2012-11-05 17:20:52
|
On Mon, Nov 5, 2012 at 9:06 PM, John Reiser <jr...@bi...> wrote: >> ==14178== Invalid read of size 2 >> ==14178== at 0x4A094C0: memcpy@@GLIBC_2.14 (mc_replace_strmem.c:653) > >> ==14178== Address 0x8b3256e is 750 bytes inside a block of size 40,704 alloc'd >> ==14178== at 0x4A074CD: malloc (vg_replace_malloc.c:236) >> ==14178== by 0x4A07657: realloc (vg_replace_malloc.c:525) > > Something peculiar is happening because of the realloc(). > > Re-run with --track-origins=yes. > > Re-run together with vgdb. Stop at this complaint, and use vgdb to print > the status of the entire buffer. Thanks, but I didn't understand the last part. What exactly do I need to run to "print the status of the entire buffer"? I'm running with --track-origins=yes --db-attach=yes my 'man valgrind' has no mention of vgdb. > > -- > > > ------------------------------------------------------------------------------ > 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 |