llnl / llnl/Quicksilver

Message from cuda-memcheck

Open
#48 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
47
Forks
37
PR merge metrics
No merged PRs in 30d

Description

I built the application with the options below and ran on a P100 GPU.

-O2 -DHAVE_CUDA -x cu -dc

cuda-memcheck shows the following message. When similar message can be reproduced, would you please update the kernels ? If I don't build/run the program appropriately, please let me know.

Thanks

cuda-memcheck ./qs

========= Invalid __global__ read of size 8
=========     at 0x000002e8 in CycleTrackingGuts(MonteCarlo*, int, ParticleVault*, ParticleVault*)
=========     by thread (127,0,0) in block (194,0,0)
=========     Address 0x7f153e0002e8 is out of bounds
=========     Device Frame:CycleTrackingKernel(MonteCarlo*, int, ParticleVault*, ParticleVault*) (CycleTrackingKernel(MonteCarlo*, int, ParticleVault*, ParticleVault*) : 0xa0)
=========     Saved host backtrace up to driver entry point at kernel launch time
=========     Host Frame:/lib64/libcuda.so.1 (cuLaunchKernel + 0x34e) [0x2d725e]
=========     Host Frame:./qs [0x36feb]
=========     Host Frame:./qs [0x78d31]
=========     Host Frame:./qs [0x31358]
=========     Host Frame:./qs [0x31aaf]
=========     Host Frame:./qs [0x65dc]
=========     Host Frame:/lib64/libc.so.6 (__libc_start_main + 0xf5) [0x22555]
=========     Host Frame:./qs [0x693e]
...
...

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the report with cuda-memcheck on the P100 build using the listed options and inspect the CycleTrackingKernel and CycleTrackingGuts entry points. Trace the invalid read at thread (127,0,0) in block (194,0,0); done means the out-of-bounds access is corrected and cuda-memcheck no longer reports it.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
hpc
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.