On Fri, 2015-01-23 at 10:58 -0600, [email protected] wrote:
> Is the ioctl a call to 0x30000001 PXA3XX_GCU_SHARED_MAGIC? Anybody
> know
> of a fix to let me keep profiling, or maybe a way to see which line
> of
> source triggers the call?
In the file syswrap-generic.c, uncomment the line VG_(get...),
recompile valgrind
and then you should obtain a stacktrace that leads to this unknown
ioctl.
Philippe
if (unknown_ioctl[i] == 0) {
unknown_ioctl[i] = request;
moans--;
VG_(umsg)("Warning: noted but unhandled ioctl 0x%lx"
" with no size/direction hints.\n", request);
VG_(umsg)(" This could cause spurious value errors to
appear.\n");
VG_(umsg)(" See README_MISSING_SYSCALL_OR_IOCTL for "
"guidance on writing a proper wrapper.\n" );
//VG_(get_and_pp_StackTrace)(tid, VG_(clo_backtrace_size));
return;
}
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
