Re: [Valgrind-developers] valgrind: Unrecognised instruction error

[Nicholas N. <n.n...@gm...>]

John: I suggest you temper your tone. Mahin is a newcomer who has asked a
question in good faith, and doesn't deserve an aggressive reply.

Mahin: As the error message says: "Your program has a bug and erroneously
jumped to a non-codelocation.  If you are running Memcheck and you just saw
a

warning about a bad jump, it's probably your program's fault."


I suggest addressing all the errors reported by Valgrind prior to the
"Unrecognised instruction" message. I also suggest checking the return
value of `fopen` calls for errors.


As for profiling source code, Cachegrind and Callgrind are two tools that
come with Valgrind that are good for this. You can read about them in the
user manual. `perf` is also a good profiling tool, as John mentioned.


Finally, there is a valgrind-users email list that is more appropriate for
this kind of question. This list (valgrind-developers) is more about the
development of Valgrind itself, rather than its use.


Nick

On Thu, 20 Oct 2022 at 00:49, John Reiser <jr...@bi...> wrote:

> On 10/19/22 01:40, Mahin Pandya wrote:
> > I am getting below error while running Valgrind, not sure if this is bug
> in Valgrind, application is build using Wine lib.
> >
> > Can someone check this?
> >
> > ---------------------
> >
> > …
> >
> > ==2214549== Invalid write of size 8
> >
> > ==2214549==    at 0x46C0040: setup_raise_exception (signal_x86_64.c:2158)
> >
> > ==2214549==    by 0x46C0653: segv_handler (signal_x86_64.c:2626)
> >
> > ==2214549==    by 0x407641F: ??? (in /usr/lib/x86_64-linux-gnu/
> libpthread-2.31.so)
> >
> > ==2214549==  Address 0x22fbd0 is in a rw- anonymous segment
> [[snip]]
>
> This query is so defective that we'll just ignore it until you fix it.
>
> 1. Which version of valgrind?  Report the output from "valgrind --version".
> Where did you get it?  If self-built from source then report the git commit
> hash and date.  If pre-built from a software distribution, then report
> the name and version of the distribution, and the package name and version.
>
> 2. Which version of Wine lib?  Also give the URL for download of the
> software
> and installation instructions.
>
> 3. Which execution environment?  Report the output from "sed 10q
> /proc/cpuinfo"
> and the VM booting banner from early lines of "dmesg".  It really does
> matter
> which actual or Virtual Machine.
>
> 4. Which underlying physical hardware (Intel or AMD)?  [Perhaps the same
> as #3.]
>
> >
> > Is there option I could use Valgrind for profiling source code? Any
> pointers/suggestion are welcome.
>
> DO NOT start a profiling project using valgrind.  Instead, start with
> 'perf'
> which is vastly more capable, flexible, and fast.
>
>
>
> _______________________________________________
> Valgrind-developers mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-developers
>