On Mon, Jan 26, 2009 at 11:34 PM, tic tac <hotsbl...@hotmail.com> wrote: >> Date: Thu, 15 Jan 2009 16:52:15 +0100 >> From: bart.vanass...@gmail.com >> To: hotsbl...@hotmail.com >> Subject: Re: [Valgrind-users] disInstr(ppc): unhandled instruction: >> 0x7D20009... on PPC 440EPX >> CC: valgrind-users@lists.sourceforge.net >> >> On Thu, Jan 15, 2009 at 4:18 PM, tic tac <hotsbl...@hotmail.com> wrote: >> > In regards to the following bug: >> > >> > http://bugs.kde.org/show_bug.cgi?id=180513 >> > >> > I am trying to gather information as to where I should start if I want >> > to >> > pinpoint which lines of code are leading to this problem. >> > >> > Also is there any documentation about fixing these unhandled >> > instructions? >> >> The following Valgrind flags will be helpful while modifying VEX: >> --trace-flags and --trace-notbelow. These flags tell Valgrind to show >> how it translates assembly instructions into the intermediate >> representation through VEX and the other way around. An example: >> >> $ ./vg-in-place --tool=none --trace-flags=10000001 --trace-notbelow=0 >> /bin/date >> > I did the run with the mentioned options, I am getting 7Mo compressed in a > log file. How do I go from there?
Maybe I was not clear enough: the command-line options --trace-flags and --trace-notbelow are a.o. helpful for verifying whether modifications of the VEX library are OK -- I was not asking to send me the output of a Valgrind run with these options enabled. Bart. ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
