|
From: Logan G. <log...@gm...> - 2006-01-12 20:37:11
|
=3D=3D1319=3D=3D Warning: set address range perms: large range 2147476646, =
a 0, v 0
Memcheck: mc_main.c:584 (set_address_range_perms): the 'impossible' happene=
d.
=3D=3D1319=3D=3D at 0x70015010: report_and_quit (m_libcassert.c:136)
=3D=3D1319=3D=3D by 0x70015260: vgPlain_assert_fail (m_libcassert.c:199)
=3D=3D1319=3D=3D by 0x70003E7C: set_address_range_perms (mc_main.c:573)
=3D=3D1319=3D=3D by 0x7004E44C: vgSysWrap_generic_sys_read_after
(priv_types_n_macros.h:249)
=3D=3D1319=3D=3D by 0x70052370: vgPlain_post_syscall (syswrap-main.c:934=
)
=3D=3D1319=3D=3D by 0x70052140: vgPlain_client_syscall (syswrap-main.c:8=
60)
=3D=3D1319=3D=3D by 0x7003D268: handle_syscall (scheduler.c:624)
=3D=3D1319=3D=3D by 0x7003D670: vgPlain_scheduler (scheduler.c:725)
=3D=3D1319=3D=3D by 0x700533E4: thread_wrapper (syswrap-linux.c:86)
=3D=3D1319=3D=3D by 0x70053518: run_a_thread_NORETURN (syswrap-linux.c:1=
19)
=3D=3D1319=3D=3D by 0x70053668: vgModuleLocal_start_thread_NORETURN
(syswrap-linux.c:206)
=3D=3D1319=3D=3D by 0x7005FEC0: (within /usr/local/lib/valgrind/ppc32-li=
nux/memcheck)
=3D=3D1319=3D=3D by 0x4483BA1C: ???
On 1/12/06, Logan Gabriel <log...@gm...> wrote:
> Yes that is correct, The system call is returning -7002 in one
> condition.... and -7001 in a different condition. I will go change
> the code and re run in an hour or two after lunch... thanks for the
> prompt replies =3D).
>
> On 1/12/06, Julian Seward <js...@ac...> wrote:
> >
> > Cancel that last message - I didn't read the backtrace carefully
> > enough. It's handling a read syscall, but what _seems_ (note,
> > superficial analysis :-) to be happening is that the kernel is
> > saying the syscall succeeded and read -7002 bytes of data. Cool.
> >
> > The immediate trigger of the problem is this
> >
> > POST(sys_read)
> > {
> > vg_assert(SUCCESS);
> > POST_MEM_WRITE( ARG2, RES );
> > }
> >
> > (syswrap-generic.c:4785). What happens if you change "RES" to
> > "0x7FFFFFFF & (RES)" ?
> >
> > J
> >
> >
> > > > Memcheck: mc_main.c:584 (set_address_range_perms): the 'impossible'
> > > > happened. =3D=3D2272=3D=3D at 0x70015010: report_and_quit (m_lib=
cassert.c:136)
> > > > =3D=3D2272=3D=3D by 0x70015260: vgPlain_assert_fail (m_libcasser=
t.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-ma=
in.c:934)
> > > > =3D=3D2272=3D=3D by 0x7005213C: vgPlain_client_syscall (syswrap-=
main.c:860)
> > > > =3D=3D2272=3D=3D by 0x7003D268: handle_syscall (scheduler.c:624)
> > > > =3D=3D2272=3D=3D by 0x7003D670: vgPlain_scheduler (scheduler.c:7=
25)
> > > > =3D=3D2272=3D=3D by 0x700533E0: thread_wrapper (syswrap-linux.c:=
86)
> > > > =3D=3D2272=3D=3D by 0x70053514: run_a_thread_NORETURN (syswrap-l=
inux.c:119)
> > > > =3D=3D2272=3D=3D by 0x70053664: vgModuleLocal_start_thread_NORET=
URN
> > >
> > > Well, umm. The problem is certainly syscall related, but this stack
> > > trace lacks the critical frame which would indicate which syscall it
> > > is. (What was really called from syswrap-main.c:934?)
> > >
> > > Can you rerun with --trace-syscalls=3Dyes. This should give an
> > > strace-style log of syscalls. Just send the couple of lines
> > > prior to the "Warning" line.
> > >
> > > J
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.net email is sponsored by: Splunk Inc. Do you grep through lo=
g
> > > files for problems? Stop! Download the new AJAX search engine that =
makes
> > > searching your log files as easy as surfing the web. DOWNLOAD SPLUN=
K!
> > > 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.
>
--
Thanks;
Logan Gabriel.
|