$ cat foo.s
.byte 0x66,0xF,0x3A,0x22
.byte 0,0,0,0
#
# For x86_64 on x86_64
#
$ gcc --version
gcc (GCC) 12.2.1 20221121 (Red Hat 12.2.1-4)
$ gcc -c foo.s
$ file foo.o
foo.o: ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV), stripped
$ gdb foo.o
GNU gdb (GDB) Fedora 12.1-2.fc36
(gdb) x/i 0
0
> On 16 Feb 2023, at 00:37, Anand K R wrote:
>
> 0x66 0xF 0x3A 0x22
>
I can’t see what that disassembles to.
Can you tell us what CPU exactly this is for, and which OS and compiler you are
using?
Do you get any call stacks (for Valgtind itself or the test exe)?
Lastly, can you provide a
Hi,
I am getting the following error when using valgrind version 20. It
terminates with sigill. Request for any help in resolving this.
vex x86->IR: unhandled instruction bytes: 0x66 0xF 0x3A 0x22
Regards,
Anand
___
Valgrind-users mailing list
V
mihir amrelia wrote:
file /var/tmp/cavium/bin/valgrind
/var/tmp/cavium/bin/valgrind: ELF 64-bit MSB executable, MIPS, MIPS64 rel2
version 1 (SYSV), dynamically linked, interpreter /lib64-f, for GNU/Linux
2.6.32, not stripped
How to fix this?
Tom Hughes via Valgrind-users wrote:
No idea - th
No idea - that will be down to your cross build toolchain.
Tom
On 10/01/2021 18:21, mihir amrelia wrote:
Tom,
Thanks a lot for your response.
Yes, it doesn't look like the one I should be expecting..
file /var/tmp/cavium/bin/valgrind
/var/tmp/cavium/bin/valgrind: ELF 64-bit MSB executable, MI
Tom,
Thanks a lot for your response.Yes, it doesn't look like the one I should be
expecting..
file /var/tmp/cavium/bin/valgrind/var/tmp/cavium/bin/valgrind: ELF 64-bit MSB
executable, MIPS, MIPS64 rel2 version 1 (SYSV), dynamically linked, interpreter
/lib64-f, for GNU/Linux 2.6.32, not strippe
On 07/01/2021 10:54, mihir amrelia via Valgrind-users wrote:
I am trying to get valgrind running on cavium octeon 3 processor.
Couldn't find any specific build configs for this other than some hints
on the valgrind wiki.
*
*
*
The steps executed to build valgrind for cavium were (on x86_64 h
Hi,
I am trying to get valgrind running on cavium octeon 3 processor.
Couldn't find any specific build configs for this other than some hints on the
valgrind wiki.
The steps executed to build valgrind for cavium were (on x86_64 host):
export CC=/opt/cavium-64bit/tools-3535/bin/mips64-octeon-li
Hi
I am trying to cross compile the valgrind for arm. Need help me with the
options for build /target and host?
I am trying different options but unable to succeed in the build
My build machine is
uname -a
Linux in-mvlb24 2.6.32-431.el6.x86_64 #1 SMP Fri Nov 22 03:15:09 UTC 2013
x86_64 x86_64 x8
Hi:
There is valgrind assert failure when valgrind run the process.
But it does not always occurred ,sometimes.
There is only two thread , One the thread is sleeping and
waiting the message, another thread is running.
I do not how to debug it, ca
Hi everybody,
I'm new in profiling and got stuck in analyzing cachegrind's output.
Any help and hints for further profiling strategies are appreciated!
It is not so important for me to get the problem at hand optimized, but
to get some insights into profiling.
Background:
I tried to implement a p
t; well. (You'd likely also need to be saying: -msoft-float )
>
> Thanks & Regards,
> Anmol P. Paralkar
>
> From: selvam [mailto:sathakse...@gmail.com]
> Sent: Sunday, March 24, 2013 1:30 PM
> To: valgrind-users@lists.sourceforge.net
> Subject: [Valgrind-users] Need
On Sun, Mar 24, 2013 at 11:29 AM, selvam wrote:
> I have cross compiled Valgrind (3.8.1) for powerPC architecture (QorIQ
> processor - e500), while running the valgrind, it exited immediately with
> error message " unhandled instruction".
> Googled for this issue, seems like floating point instruc
Hi Team,
I have cross compiled Valgrind (3.8.1) for powerPC architecture (QorIQ
processor - e500), while running the valgrind, it exited immediately with
error message " unhandled instruction".
Googled for this issue, seems like floating point instructions (SPE and
AltiVec) of e500 are not support
>> ==3898== Memcheck, a memory error detector
>> ==3898== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
>> ==3898== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright info
>> ==3898== Command: ./mkvariable_key
[snip]
>> ==3898== Conditional jump or move depends on unin
Consider building everything in debug mode. This will give you line
numbers.
Brian
On Apr 20, 2012 1:59 AM, "achinta gogoi" wrote:
>
> Sir,
>
> Please help to solve bellow errors. Thanks
> with Regard
> Achinta Kumar gogoi
>
> - Forwarded Message -
> *From:* Julian Seward
> *To:* a
Sir,
Please help to solve bellow errors. Thanks
with Regard
Achinta Kumar gogoi
- Forwarded Message -
From: Julian Seward
To: achinta gogoi
Sent: Thursday, April 19, 2012 6:39 PM
Subject: Re: Need Help to fix to below error
Please send this to the valgrind-users mailing list, no
Hi all,
I am working on I.MX51 EVK Babbage board, I found my application eats up much
memory and wants to use valgrind to check the memory status.
Founded source code from valgrind.org. BSP gcc position
/opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueabi/bin/arm-none-linux
On Saturday 08 May 2010, n179911 wrote:
> I have run callgrind with my application like this
> "valgrind --tool=callgrind MyApplication"
> and then call 'callgrind_annotate --auto=yes ./callgrind.out.2489'
>
>
> I see output like
>
> 768,097,560 PROGRAM TOTALS
>
> -
n179911, 08.05.2010:
> Hi,
>
> I have run callgrind with my application like this
> "valgrind --tool=callgrind MyApplication"
> and then call 'callgrind_annotate --auto=yes ./callgrind.out.2489'
you want to use KCacheGrind, really.
--
Milian Wolff
m...@milianw.de
http://milianw.de
signature.as
Hi,
I have run callgrind with my application like this
"valgrind --tool=callgrind MyApplication"
and then call 'callgrind_annotate --auto=yes ./callgrind.out.2489'
I see output like
768,097,560 PROGRAM TOTALS
Hi,
I'm writing a new tool that will generate a data dependency graph(on
x86 Ubuntu). As the first step, I have modified the 'instrument' function
inside 'none' tool so that you write to a shadow memory for each 'store'
statement as follows.
case Ist_Store:{
di = unsafeIRDirty_0_N(
Hi All,
I Created a output file foe a executable using
tool valgrind --tool=callgrind ./myexecutable
it is giving library functions also in the ouput i just want to
detect that library functions.Because my objective is see the call graph in
kcachegrind with onl
Hello,
First of all, I am a novice.
I just want to check all memory used of a c program and think that
valgrind can give me that.
The problem I encounter now are
1. using this valgrind command
$ valgrind -v --tool=massif myprog
on the cluster of my university (version 3.3.1) and there is no
On Wed, Apr 15, 2009 at 6:41 AM, Nicholas Nethercote
wrote:
>
> It's almost certainly caused by heap corruption due to the errors
> Valgrind reports about your program. If you fix those, this crash
> will almost certainly go away.
I just clarified the abort/crash message, making this possibility
Hi graham
Are you sure that all libraries needed by valgrind are accessible
on all your nodes? If it is Open MPIy wrote:
> On Wed, Apr 15, 2009 at 6:31 AM, Graham Mark wrote:
>>
>> I'm trying to track down the cause of a seg fault in my MPI program.
>> Here's what happens with valgrind.
>>
>> % m
On Wed, Apr 15, 2009 at 6:31 AM, Graham Mark wrote:
>
> I'm trying to track down the cause of a seg fault in my MPI program.
> Here's what happens with valgrind.
>
> % mpirun -n 27 ../../valgrind-3.4.1/bin/valgrind --kernel-
> variant=bproc mc3_op
> ERROR: ld.so: object '/usr/projects/dark/gam/val
I'm trying to track down the cause of a seg fault in my MPI program.
Here's what happens with valgrind.
% mpirun -n 27 ../../valgrind-3.4.1/bin/valgrind --kernel-
variant=bproc mc3_op
ERROR: ld.so: object '/usr/projects/dark/gam/valgrind/amd64-linux/
libmpiwrap.so' from LD_PRELOAD cannot be p
28 matches
Mail list logo
