|
From: Joshua Moore-O. <jo...@ch...> - 2004-07-14 02:48:57
|
I get this output, and a message to submit this data.. I have no idea what it means, but here it is.. How do I work around this? Thanks, Josh. Valgrind version: 2.1.1 Operating system: Gentoo ==24017== Warning: set address range perms: large range 134217728, a 0, v 1 valgrind: vg_malloc2.c:1008 (vgPlain_arena_malloc): Assertion `new_sb != ((void *)0)' failed. ==24017== at 0xB802FA70: vgPlain_skin_assert_fail (vg_mylibc.c:1211) ==24017== by 0xB802FA6F: assert_fail (vg_mylibc.c:1207) ==24017== by 0xB802FADD: vgPlain_core_assert_fail (vg_mylibc.c:1218) ==24017== by 0xB802BBEF: vgPlain_arena_malloc (vg_malloc2.c:535) ==24017== by 0xB802C741: vgPlain_cli_malloc (vg_malloc2.c:1393) ==24017== by 0xB02474E7: vgSkin_malloc (mac_malloc_wrappers.c:181) ==24017== by 0xB8012097: do_client_request (vg_scheduler.c:2886) ==24017== by 0xB800E3E0: vgPlain_scheduler (vg_scheduler.c:1065) ==24017== by 0xB802A2E3: main (vg_main.c:2994) sched status: Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0 ==24017== at 0x3C01C40D: malloc (vg_replace_malloc.c:105) ==24017== by 0x3C01CC88: realloc (vg_replace_malloc.c:154) ==24017== by 0x804949F: FreeTdsxx_convertBufferResize (FreeTdsxx_convertBufferResize.c:6) ==24017== by 0x80492E6: FreeTdsxx_colValFromIdx (FreeTdsxx_colValFromIdx.c:23) ==24017== by 0x804AB2A: main (main.c:48) |
|
From: Joshua Moore-O. <jo...@ch...> - 2004-07-14 03:10:49
|
I was allocating a stupidly large buffer, that is the cause of the error... although, as a suggestion it could be a little more specific in the error. Josh. On July 13, 2004 10:48 pm, Joshua Moore-Oliva wrote: > I get this output, and a message to submit this data.. I have no idea what it means, but here it is.. > > How do I work around this? > > Thanks, Josh. > > Valgrind version: 2.1.1 > Operating system: Gentoo > > ==24017== Warning: set address range perms: large range 134217728, a 0, v 1 > > valgrind: vg_malloc2.c:1008 (vgPlain_arena_malloc): Assertion `new_sb != ((void *)0)' failed. > ==24017== at 0xB802FA70: vgPlain_skin_assert_fail (vg_mylibc.c:1211) > ==24017== by 0xB802FA6F: assert_fail (vg_mylibc.c:1207) > ==24017== by 0xB802FADD: vgPlain_core_assert_fail (vg_mylibc.c:1218) > ==24017== by 0xB802BBEF: vgPlain_arena_malloc (vg_malloc2.c:535) > ==24017== by 0xB802C741: vgPlain_cli_malloc (vg_malloc2.c:1393) > ==24017== by 0xB02474E7: vgSkin_malloc (mac_malloc_wrappers.c:181) > ==24017== by 0xB8012097: do_client_request (vg_scheduler.c:2886) > ==24017== by 0xB800E3E0: vgPlain_scheduler (vg_scheduler.c:1065) > ==24017== by 0xB802A2E3: main (vg_main.c:2994) > > sched status: > > Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0 > ==24017== at 0x3C01C40D: malloc (vg_replace_malloc.c:105) > ==24017== by 0x3C01CC88: realloc (vg_replace_malloc.c:154) > ==24017== by 0x804949F: FreeTdsxx_convertBufferResize (FreeTdsxx_convertBufferResize.c:6) > ==24017== by 0x80492E6: FreeTdsxx_colValFromIdx (FreeTdsxx_colValFromIdx.c:23) > ==24017== by 0x804AB2A: main (main.c:48) > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > |
|
From: Howard C. <hy...@sy...> - 2004-07-14 03:13:48
|
Joshua Moore-Oliva wrote: > I get this output, and a message to submit this data.. I have no idea what it means, but here it is.. It means you ran out of memory. valgrind 2.1.1 appears to be quite a memory pig compared to previous versions. > How do I work around this? Installing more RAM in your computer might help. I recall reading on the -developer list that there's a patch to decrease some of valgrind's demand for RAM. Hopefully it will be publically released soon. > Thanks, Josh. > > Valgrind version: 2.1.1 > Operating system: Gentoo > > ==24017== Warning: set address range perms: large range 134217728, a 0, v 1 > > valgrind: vg_malloc2.c:1008 (vgPlain_arena_malloc): Assertion `new_sb != ((void *)0)' failed. > ==24017== at 0xB802FA70: vgPlain_skin_assert_fail (vg_mylibc.c:1211) > ==24017== by 0xB802FA6F: assert_fail (vg_mylibc.c:1207) > ==24017== by 0xB802FADD: vgPlain_core_assert_fail (vg_mylibc.c:1218) > ==24017== by 0xB802BBEF: vgPlain_arena_malloc (vg_malloc2.c:535) > ==24017== by 0xB802C741: vgPlain_cli_malloc (vg_malloc2.c:1393) > ==24017== by 0xB02474E7: vgSkin_malloc (mac_malloc_wrappers.c:181) > ==24017== by 0xB8012097: do_client_request (vg_scheduler.c:2886) > ==24017== by 0xB800E3E0: vgPlain_scheduler (vg_scheduler.c:1065) > ==24017== by 0xB802A2E3: main (vg_main.c:2994) > > sched status: > > Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0 > ==24017== at 0x3C01C40D: malloc (vg_replace_malloc.c:105) > ==24017== by 0x3C01CC88: realloc (vg_replace_malloc.c:154) > ==24017== by 0x804949F: FreeTdsxx_convertBufferResize (FreeTdsxx_convertBufferResize.c:6) > ==24017== by 0x80492E6: FreeTdsxx_colValFromIdx (FreeTdsxx_colValFromIdx.c:23) > ==24017== by 0x804AB2A: main (main.c:48) -- -- Howard Chu Chief Architect, Symas Corp. Director, Highland Sun http://www.symas.com http://highlandsun.com/hyc Symas: Premier OpenSource Development and Support |
|
From: Nicholas N. <nj...@ca...> - 2004-07-14 10:47:34
|
On Tue, 13 Jul 2004, Howard Chu wrote: >> I get this output, and a message to submit this data.. I have no idea >> what it means, but here it is.. > > It means you ran out of memory. valgrind 2.1.1 appears to be quite a memory > pig compared to previous versions. > >> How do I work around this? > > Installing more RAM in your computer might help. I recall reading on the > -developer list that there's a patch to decrease some of valgrind's demand > for RAM. Hopefully it will be publically released soon. I don't think installing more RAM would help. The issue isn't physical memory, rather address space. 2.1.1 does do not so well here; the current CVS version has some improvements in this respect, and I'm looking at improving things further. The CVS version also no longer asserts when malloc() fails, rather it just returns NULL as standard. If you really need to do big mallocs like this and Memcheck is failing, you could try Addrcheck as it uses less memory. N |