My experiences building with ICC..
#1 it failed out of the box with
checking for a supported version of gcc... no (13.1.3)
configure: error: please use gcc >= 3.0 or clang >= 2.9
I had to make some hacks in ./configure to support ICC
notclang-13.*)
{ $as_echo "$as_me:${as_lineno-$LINEN
On 9/26/2014 12:38 PM, Julian Seward wrote:
> On 09/25/2014 12:52 PM, Eliot Moss wrote:
>> I started updating the valgrind documentation to add description
>> of this new feature, and expect to submit a patch soon for
>> developer approval.
>
> https://bugs.kde.org/show_bug.cgi?id=339405
> is the b
Please see the followings. After posting my question at that moment, I
realized that I should specify the shared library name, because it's in
libc as you said. However, it didn't work using VG_Z_LIBC_SONAME.
Best regards,
Myoungkyu
===
On 09/25/2014 12:52 PM, Eliot Moss wrote:
> I started updating the valgrind documentation to add description
> of this new feature, and expect to submit a patch soon for
> developer approval.
https://bugs.kde.org/show_bug.cgi?id=339405
is the bug, yes?
J
Yes, if you get some details on how/why it fails, that would
be good. Also, filing a bug in bugzilla
(see http://www.valgrind.org/support/bug_reports.html)
will ensure your bug report doesn't get lost later on.
J
On 09/25/2014 02:58 PM, Vallevand, Mark K wrote:
> I tried that option. Doesn’t
That's a bit strange. Can you please try with the recently released
3.10.0 version, and see if you still have the problem?
Thanks.
J
On 09/25/2014 01:41 PM, lchquan wrote:
> # /opt/vg/bin/valgrind ls
> ==5290== Memcheck, a memory error detector
> ==5290== Copyright (C) 2002-2013, and GNU GPL'
You need to say what CPU this is on. For x86_64 I think this is
impossible, because all x86_64 processors support at least SSE2.
For x86 (32 bit) this might just be possible. In VEX/priv/guest_x86_toIR.c,
find the code that handles CPUID
case 0xA2: { /* CPUID */
and change it so that it
Er, this isn't good. Can you file a bug report
as described at http://www.valgrind.org/support/bug_reports.html
so that this gets tracked properly? If it just remains on the mailing
list it is likely to get forgotten.
Thanks.
J
On 09/18/2014 10:09 AM, Matthias Apitz wrote:
>
> Hello,
>
> T
On 09/23/2014 03:31 AM, Myoungkyu Song wrote:
> I have a question, which maybe was discussed. I would like to implement a
> wrapper function for standard API such as "strcpy". However, I failed to
> do. When I tested a user-defined function like "hello(char *, char *)"
> below, I successfully wr
