Re: [Valgrind-developers] none tool under gdb

[Paul F. <pj...@wa...>]

On 7/27/25 15:24, Florian Krohm wrote:
>
> I suppose people rarely debug the none tool. I found out because the 
> iropt tester runs under "none" auspices...
> Off-hand I have no idea what might be causing it.
>
Hi Florian

I think that you are just missing the --tool=none argument to the tool.

Once loaded in gdb you need to use something like

run --tool=none ./foo

(or start gdb with --args or use set args before the run).

If you leave out the "--tool=none" it will default to the memcheck 
options but with none as the tool. This isn't just a gdb thing. For 
instance (with the VALGRIND_* env vars set)

./.in_place/none-amd64-freebsd -q ./foo
--2850-- VG_USERREQ__CLIENT_CALL1: func=0x0
0x0

(I don't know why I'm getting a USERREQ moan, it's caused by an ifunc)

and

./.in_place/none-amd64-freebsd -q --tool=none ./foo
0x4e09000


A+

Paul