|
From: Logan G. <log...@gm...> - 2006-01-12 17:49:40
|
Here is the output: =3D=3D2272=3D=3D Warning: set address range perms: large range 4294960294, = a 0, v 0 Memcheck: mc_main.c:584 (set_address_range_perms): the 'impossible' happene= d. =3D=3D2272=3D=3D at 0x70015010: report_and_quit (m_libcassert.c:136) =3D=3D2272=3D=3D by 0x70015260: vgPlain_assert_fail (m_libcassert.c:199) =3D=3D2272=3D=3D by 0x70003E7C: set_address_range_perms (mc_main.c:573) =3D=3D2272=3D=3D by 0x7004E448: vgSysWrap_generic_sys_read_after (priv_types_n_macros.h:249) =3D=3D2272=3D=3D by 0x7005236C: vgPlain_post_syscall (syswrap-main.c:934= ) =3D=3D2272=3D=3D by 0x7005213C: vgPlain_client_syscall (syswrap-main.c:8= 60) =3D=3D2272=3D=3D by 0x7003D268: handle_syscall (scheduler.c:624) =3D=3D2272=3D=3D by 0x7003D670: vgPlain_scheduler (scheduler.c:725) =3D=3D2272=3D=3D by 0x700533E0: thread_wrapper (syswrap-linux.c:86) =3D=3D2272=3D=3D by 0x70053514: run_a_thread_NORETURN (syswrap-linux.c:1= 19) =3D=3D2272=3D=3D by 0x70053664: vgModuleLocal_start_thread_NORETURN (syswrap-linux.c:206) =3D=3D2272=3D=3D by 0x7005FEBC: (within /usr/local/lib/valgrind/ppc32-li= nux/memcheck) =3D=3D2272=3D=3D by 0x44887A1C: ??? =3D=3D2272=3D=3D by 0x700635F8: myvprintf_str (m_debuglog.c:266) On 1/12/06, Julian Seward <js...@ac...> wrote: > > > I'm not sure if this helps or not but I saw the large range 4294960294 > > before I wrote the ioctl wrappers. > > Ok, so it's a pre-existing bug :-) Perhaps an endianness thing -- the > ppc port hasn't been hammered as much as the x86/amd64 ports. > > > > > =3D=3D1953=3D=3D Warning: set address range perms: large range 4294= 960294, > > We need to know why this happened. Can you find the place this is > printed (mc_main.c, around about line 490) and put "tl_assert(0)" > immediately after it; rebuild; rerun. This should give a backtrace showi= ng > how V got there. My feeling is (and this could be wrong) that once > we know that, the bug should be relatively simple to fix. > > Alternatively .. make a simple C test program which shows the problem > and can be examined at this end. > > J > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi= les > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > -- Thanks; Logan Gabriel. |