mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Valgrind Support for Arm Architecture - Illegal Instruction Bug
Date: Mon, 26 Mar 2018 08:24:52 +0200	[thread overview]
Message-ID: <20180326062452.tx7fos5y4trdplhk@pengutronix.de> (raw)
In-Reply-To: <ACB14472E10C9943B95FFCAC2AAEE43238ECBC@AT-ESXVM-271.fronius.com>

Hi,

On Tue, Mar 20, 2018 at 02:44:29PM +0000, Jakovljevic Miljenko wrote:
> I am using PTXdist 2016.10.0 with the following architecture arm-1136jfs-linux-gnueabihf.
> 
> PTXdist installs valgrind version 3.11 per default. When one runs valgrind
> the following message occurs: " Illegal instruction"
> 
> According to the forums, https://bbs.archlinux.org/viewtopic.php?id=36318
> this was supposed to have been corrected in version valgrind 3.3 - (at least on the PC).

"Illegal instruction" is a very architecture specific error. Changes for
x86 have no impact on ARM.

> What is the current status of valgrind support with ptxdist?

At least according to the website[1] ARMv6 (arm-1136jfs is a ARMv6 Core)
is not supported at all by valgrind. There is nothing we can do about that
in PTXdist.

Michael

[1] http://valgrind.org/info/platforms.html

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2018-03-26  6:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20 14:44 Jakovljevic Miljenko
2018-03-26  6:24 ` Michael Olbrich [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180326062452.tx7fos5y4trdplhk@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox