[valgrind] [Bug 476277] valgrind not able to startup in arm 64board using 32bit tool chain

2023-11-21 Thread rama kanth
https://bugs.kde.org/show_bug.cgi?id=476277

--- Comment #2 from rama kanth  ---
"/usr/bin/uname -a"

in my target board gives below information

Linux dsldevice 4.19.275 #1 SMP PREEMPT Sun Nov 12 23:58:57 EST 2023 aarch6.

Platform details should be changed here . Its not a RHEL which is running
in my target board.
It's customized linux os given by the board vendor.





On Sat, Nov 4, 2023 at 9:34 PM John Reiser  wrote:

> https://bugs.kde.org/show_bug.cgi?id=476277
>
> John Reiser  changed:
>
>What|Removed |Added
>
> 
>  CC||jrei...@bitwagon.com
>
> --- Comment #1 from John Reiser  ---
> This bug report itself could be improved by specifying the versions used
> on the
> "arm 64 board."   Such version information typically helps a lot to
> reproduce
> the problem, which helps understand and fix it faster.
> In the header of this bug report, the Platform is identified as "RedHat
> Enterprise Linux".  Please specify which release, which is contained in
> /etc/os-release on the arm64 board (not on the development environment).
> Another helpful information is given by running "/usr/bin/uname -a"
> Then, RedHat (and Fedora, and SuSE) uses the RPM package manager to track
> installed software.  Please specify the package involved. This information
> can
> be found by running a query using /usr/bin/rpm on the arm64 board;
> something
> like:
> $ rpm -qf /lib64/ld-linux-aarch.so.3   # use the actual path for
> ld-linux
> on the arm64 board
> glibc-2.37-13.el9.aarch   # example package name; please report the
> actual
> output from "rpm -qf /path/to/ld-linux".
>
> --
> You are receiving this mail because:
> You reported the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 476277] valgrind not able to startup in arm 64board using 32bit tool chain

2023-11-04 Thread John Reiser
https://bugs.kde.org/show_bug.cgi?id=476277

John Reiser  changed:

   What|Removed |Added

 CC||jrei...@bitwagon.com

--- Comment #1 from John Reiser  ---
This bug report itself could be improved by specifying the versions used on the
"arm 64 board."   Such version information typically helps a lot to reproduce
the problem, which helps understand and fix it faster.
In the header of this bug report, the Platform is identified as "RedHat
Enterprise Linux".  Please specify which release, which is contained in
/etc/os-release on the arm64 board (not on the development environment). 
Another helpful information is given by running "/usr/bin/uname -a"
Then, RedHat (and Fedora, and SuSE) uses the RPM package manager to track
installed software.  Please specify the package involved. This information can
be found by running a query using /usr/bin/rpm on the arm64 board; something
like:
$ rpm -qf /lib64/ld-linux-aarch.so.3   # use the actual path for ld-linux
on the arm64 board
glibc-2.37-13.el9.aarch   # example package name; please report the actual
output from "rpm -qf /path/to/ld-linux".

-- 
You are receiving this mail because:
You are watching all bug changes.