Thanks John. It is memory-mapped hardware device. I will debug more and
would update you.
On Tue, Sep 19, 2017 at 3:00 PM, John Reiser <jrei...@bitwagon.com> wrote:
> My code access memory-address range starting from 0x8001180000000000. This
>> is legitimate access.
>>
>
> But *what* does it access? Is it a memory-mapped hardware device, or is
> it real RAM?
> Actual memory can be accessed in smaller or larger pieces in any order,
> and give consistent answers. Many hardware devices cannot. If
> 0x8001180000000000
> is a hardware device, then put a logic analyzer on the bus and find out
> exactly what is going on.
> If it's supposed to be actual RAM, then invoke valgrind with
> --trace-notbelow=0 --trace-flags=10000000
> (warning: many megabytes of output) and examine the accesses there.
>
> --
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Valgrind-users mailing list
> Valgrind-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
