[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: gEDA: VPI in Icarus Verilog
How odd. I look in the Standard and in Sutherland's Big
Blue Book (BBB) and nowhere do I see it explicitly stated
that cbValueChange is good for more than a single event.
However, I believe that is expected behavior as the example
usage in the BBB does not re-register itself every time it
is called and is expected to be called with every change
in value of the monitored signal.
Best regards,
Jason
--
Jason Doege
Director, Design Link Technology
Inovys, Corp. Phone (512) 422-9483
11417 Carnelian Dr. Fax (512) 292-8958
Austin, TX 78739 email jason_doege@inovys.com
-----Original Message-----
From: owner-geda-dev@seul.org [mailto:owner-geda-dev@seul.org]On Behalf
Of Stephen Williams
Sent: Monday, March 04, 2002 9:50 AM
To: geda-dev@seul.org
Subject: Re: gEDA: VPI in Icarus Verilog
mjarabek@istop.com said:
> 1) When a callback is registered using vpi_register_cb() who allocates/
> owns the memory pointed to by the argument? The Verilog-1995 standard
> is not clear on this point, except to say that when the callback is
> called the pointer to the cb_data structure is not a pointer to the
> same structure as was passed to the vpi_register_cb() function.
The simulator allocates and manages that memory. It automatically
releases it when the callback memory is no longer needed.
mjarabek@istop.com said:
> 2) Callbacks only seem to happen once, yet the standard implies that
> once a callback has been installed it keeps getting called.
Could I have got that all wrong? I'll have to research this.
mjarabek@istop.com said:
> I added a call to `dlerror()' and discovered the real error.
I have the same problem. I'd gladly apply a patch to fix this:-)
--
Steve Williams "The woods are lovely, dark and deep.
steve at icarus.com But I have promises to keep,
steve at picturel.com and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep."
abuse@xo.com
uce@ftc.gov