Bug 355197 - Too strong assert in variable debug info code (chase_cuOff, assert)
Summary: Too strong assert in variable debug info code (chase_cuOff, assert)
Status: CONFIRMED
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (show other bugs)
Version: 3.10 SVN
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-11 15:57 UTC by Antonio J. Peña
Modified: 2017-05-05 14:23 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Suggested workaround (1.12 KB, patch)
2015-11-11 15:58 UTC, Antonio J. Peña
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Antonio J. Peña 2015-11-11 15:57:12 UTC
I'm finding a code which makes the case Te_TyArray in ML_(sizeOfType) to blowup in an assert.

I'm attaching a suggested patch which would soften things out and allow the execution to continue. Anyway, the problem is likely related with the debug info reader, since I'm getting the famous "chase_cuOff: no entry for ..."

I'm using a pretty complex code, but if you're interested I can attach it as well or try to find a minimal code causing the problem.

Best,
  Antonio J. Peña
  Barcelona Supercomputing Center

Reproducible: Always

Steps to Reproduce:
1. Compile MiniMD from mantevo.org
2. Execute valgrind with --read-var-info=yes

Actual Results:  
Assert failed. Execution aborted.

Expected Results:  
Try to continue execution.
Comment 1 Antonio J. Peña 2015-11-11 15:58:17 UTC
Created attachment 95443 [details]
Suggested workaround
Comment 2 Antonio J. Peña 2015-11-11 15:59:23 UTC
BTW, this is current trunk, 3.12.0.SVN (r15725).
  --Antonio
Comment 3 Ivo Raisr 2017-05-05 14:23:40 UTC
Please could you provide a reproducible test case? The proposed patch itself looks plausible.