Closed
Bug 699363
Opened 13 years ago
Closed 6 years ago
Within VMPI code, assert calls are acting (or failing to act) in suspcious manner
Categories
(Tamarin Graveyard :: Virtual Machine, defect)
Tamarin Graveyard
Virtual Machine
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: pnkfelix, Unassigned)
Details
From Bug 698085, comment 14:
One mystery: why did these failures only come up on Mac64?
- I had assumed when I added the include of VMAssert.h (comment 9) that the reason we only saw failures on mac64 is that the other platforms were setting up the headers to introduce the assert function (and presumably enable it on debug builds).
- But after I added that include of VMAssert.h, the Mac64 builds started failing due to what appears to be a logic error in the assert.
- But no other build failed.
This indicates to me that it is likely the calls to assert were not happening on any platforms except Mac64. This means that there is something wrong on our debug builds, at least with respect to calls to assert() within VMPI support code.
I don't know exactly what is wrong. I strongly suspect it has something to do with the attempt to do away with our own assert routine and switching to using the host provided assert.h; see Bug 645878, comment 33, Bug 645878, comment 34, Bug 645878, comment 35, Bug 645878, comment 38, and so on.
It would be good to resolve this mystery. But that is not a job for this ticket.
Comment 1•6 years ago
|
||
Tamarin isn't maintained anymore. WONTFIX remaining bugs.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•