|
From: Dilip M. R. <Dil...@kp...> - 2007-10-08 07:21:27
|
Hi,
I have checked out Valgrind code from SVN.=20
I am trying to add a dummy tool. I am referring "Writing New Tool" =
section of the user manual.
I am successful with aclocal, autoheader, automake autoconf and =
configure stages, "Make install" is exiting after generating following =
errors:
In file included from pub_core_debuglog.h:50,
from launcher.c:48:
../include/pub_tool_basics.h:47:31: error: libvex_basictypes.h: No such =
file or directory
In file included from pub_core_debuglog.h:50,
from launcher.c:48:
../include/pub_tool_basics.h:77: error: expected =E2=3D=E2, =E2,=E2, =
=E2;=E2, =E2asm=E2 or =E2__attribute__=E2 before =E2Off64T=E2
../include/pub_tool_basics.h:92: error: expected =E2=3D=E2, =E2,=E2, =
=E2;=E2, =E2asm=E2 or =E2__attribute__=E2 before =E2ThreadId=E2
../include/pub_tool_basics.h:119: error: expected =
specifier-qualifier-list before =E2Bool=E2
In file included from launcher.c:48:
pub_core_debuglog.h:59: error: expected =E2)=E2 before =E2level=E2
pub_core_debuglog.h:66: error: expected =E2=3D=E2, =E2,=E2, =E2;=E2, =
=E2asm=E2 or =E2__attribute__=E2 before =E2vgPlain_debugLog_getLevel=E2
pub_core_debuglog.h:73: error: expected =E2)=E2 before =E2level=E2
pub_core_debuglog.h:80: error: expected =E2=3D=E2, =E2,=E2, =E2;=E2, =
=E2asm=E2 or =E2__attribute__=E2 before =E2vgPlain_debugLog_vprintf=E2
In file included from pub_core_libcproc.h:40,
from launcher.c:49:
../include/pub_tool_libcproc.h:1: error: stray =E2\377=E2 in program
../include/pub_tool_libcproc.h:1: error: stray =E2\377=E2 in program
../include/pub_tool_libcproc.h:1: error: stray =E2\377=E2 in program
../include/pub_tool_libcproc.h:1: error: stray =E2\377=E2 in program
../include/pub_tool_libcproc.h:1: error: stray =E2\377=E2 in program
Due to some limitation, I have checked out the code in one system and =
had to build it in anther.=20
Is the error due to this?
But I have successfully built and installed Valgrind using the sources =
downloaded from the "Current releases" section on Valgrind site.
Kindly help me resolve the error.
With kind regards,
Dilip Malinur Ramesh
-----Original Message-----
From: Julian Seward [mailto:js...@ac...]=20
Sent: Thursday, September 06, 2007 8:21 PM
To: Dilip Malinur Ramesh
Subject: Re: Porting valgrind to SH targets
--trace-flags=3D<XXXXXXXX> show generated code? (X =3D 0|1) =
[00000000]
--trace-flags and --profile-flags values (omit the middle space):
1000 0000 show conversion into IR
0100 0000 show after initial opt
0010 0000 show after instrumentation
0001 0000 show after second opt
0000 1000 show after tree building
0000 0100 show selecting insns
0000 0010 show after reg-alloc
0000 0001 show final assembly
(Nb: you need --trace-notbelow with --trace-flags for full =
details)
On Thursday 06 September 2007 10:44, you wrote:
> Hi,
> Sorry for the confusions,
>
> I have a query,
>
> How can I see the IR generated by VEX?
> Is there any command line option we can pass while we invoke valgrind?
>
>
>
> With kind regards,
> Dilip Malinur Ramesh
> -----Original Message-----
> From: Julian Seward [mailto:js...@ac...]
> Sent: Friday, August 31, 2007 9:13 PM
> To: Dilip Malinur Ramesh
> Subject: Re: Porting valgrind to SH targets
>
>
> Why do you keep sending this mail? I have seen it 4 times now
> and it has been answered twice.
>
> J
>
> On Friday 31 August 2007 09:21, you wrote:
> > Hi,
> > I am trying to port Valgrind to Renesas SuperH targets. Using the
> > resources available on the Valgrind.org, I understood that there
>
> entire
>
> > Valgrind can be logically divided as Core and VEX implementation.
> >
> > Is my understanding correct?
> >
> > If I have to take up this porting activity, how should I have to go
> > about (like legal terms, SVN access etc)?
> >
> > If needed, where can I get additional resources or help (apart from
> > mailing list)?
> >
> > Please give me your valuable advice.
> >
> >
> >
> > With kind regards,
> > Dilip Malinur Ramesh
> >
> > -----Original Message-----
> > From: val...@li...
> > [mailto:val...@li...] On Behalf
>
> Of
>
> > Julian Seward
> > Sent: Wednesday, August 29, 2007 1:03 PM
> > To: Daniel Frampton
> > Cc: val...@li...; Steve Blackburn; =
Chris
> > January; Robin Garner
> > Subject: Re: [Valgrind-developers]Supporting the x86 INT =
instructionin
> > Valgrind
> >
> > On Friday 29 June 2007 11:06, Daniel Frampton wrote:
> > > To add to what Steve said, I saw the implementation of INT3 on the
> > > trunk, but unfortunately we use INT (0xCD) 0x40 - 0x43, and not =
INT3
> > > (0xCC).
> >
> > Just to check what needs to happen: you're expecting Valgrind to
>
> deliver
>
> > SIGSEGV to your application when encountering INT (0xCD) 0x40 - =
0x43,
> > yes?
> >
> > J
>
> =
------------------------------------------------------------------------
>
> > -
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems? Stop.
> > Now Search log events and configuration files using AJAX and a
>
> browser.
>
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > Valgrind-developers mailing list
> > Val...@li...
> > https://lists.sourceforge.net/lists/listinfo/valgrind-developers
>
> =
------------------------------------------------------------------------
>
> > -
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems? Stop.
> > Now Search log events and configuration files using AJAX and a
>
> browser.
>
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > Valgrind-developers mailing list
> > Val...@li...
> > https://lists.sourceforge.net/lists/listinfo/valgrind-developers
|