|
From: tic t. <hot...@ho...> - 2009-01-15 15:18:27
|
Hello, 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? Thank you for any help, Sebastien. |
|
From: Bart V. A. <bar...@gm...> - 2009-01-15 15:52:26
|
On Thu, Jan 15, 2009 at 4:18 PM, tic tac <hot...@ho...> 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 Bart. |
|
From: Robert W <rob...@gm...> - 2009-01-16 08:00:09
|
I would like to try out the valgrind ppc 440 binary on my machine. Could you send me the 440 compiled binary if possible? Thanks! Regards, Robert On Thu, Jan 15, 2009 at 7:18 AM, tic tac <hot...@ho...> wrote: > Hello, > > 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? > > Thank you for any help, > > Sebastien. > > ------------------------------------------------------------------------------ > 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 > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > > |
|
From: tic t. <hot...@ho...> - 2009-01-16 15:14:42
|
Hi, I can send you the steps to recompile and patched properly; as I am using a specific version of montavista ADK, I'd think this may not fit your target at all and lead to surprises if you tried to run it as such anyway. seb. > Date: Fri, 16 Jan 2009 00:00:04 -0800 > From: rob...@gm... > To: hot...@ho... > Subject: Re: [Valgrind-users] disInstr(ppc): unhandled instruction: 0x7D20009... on PPC 440EPX > CC: val...@li... > > I would like to try out the valgrind ppc 440 binary on my machine. > Could you send me the 440 compiled binary if possible? Thanks! > > Regards, > Robert > > On Thu, Jan 15, 2009 at 7:18 AM, tic tac <hot...@ho...> wrote: > > Hello, > > > > 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? > > > > Thank you for any help, > > > > Sebastien. > > > > ------------------------------------------------------------------------------ > > 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 > > Val...@li... > > https://lists.sourceforge.net/lists/listinfo/valgrind-users > > > > |
|
From: tic t. <hot...@ho...> - 2009-01-26 22:36:48
|
Hello, I did the run with the mentioned options, I am getting 7Mo compressed in a log file. How do I go from there? Sebastien. > Date: Thu, 15 Jan 2009 16:52:15 +0100 > From: bar...@gm... > To: hot...@ho... > Subject: Re: [Valgrind-users] disInstr(ppc): unhandled instruction: 0x7D20009... on PPC 440EPX > CC: val...@li... > > On Thu, Jan 15, 2009 at 4:18 PM, tic tac <hot...@ho...> 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 > > Bart. |
|
From: Bart V. A. <bar...@gm...> - 2009-01-27 15:43:55
|
On Mon, Jan 26, 2009 at 11:34 PM, tic tac <hot...@ho...> wrote: >> Date: Thu, 15 Jan 2009 16:52:15 +0100 >> From: bar...@gm... >> To: hot...@ho... >> Subject: Re: [Valgrind-users] disInstr(ppc): unhandled instruction: >> 0x7D20009... on PPC 440EPX >> CC: val...@li... >> >> On Thu, Jan 15, 2009 at 4:18 PM, tic tac <hot...@ho...> 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. |
|
From: Nicholas N. <n.n...@gm...> - 2009-01-27 23:35:55
|
On Wed, Jan 28, 2009 at 2:43 AM, Bart Van Assche <bar...@gm...> wrote: > Maybe I was not clear enough: the command-line options --trace-flags > and --trace-notbelow are a.o. helpful "a.o."? Nick |
|
From: Bart V. A. <bar...@gm...> - 2009-01-28 09:24:09
|
On Tue, Jan 27, 2009 at 10:48 PM, Nicholas Nethercote <n.n...@gm...> wrote: > On Wed, Jan 28, 2009 at 2:43 AM, Bart Van Assche > <bar...@gm...> wrote: >> Maybe I was not clear enough: the command-line options --trace-flags >> and --trace-notbelow are a.o. helpful > > "a.o."? The command-line options --trace-flags and --trace-notbelow are helpful, and probably some other options too, but I didn't check. Bart. |