| Number | 516
|
| Notify-List |
|
| Category | errata
|
| Synopsis | 27.13 and 27.31 doesn't talk about what happens with a save/restart/reset
|
| State | lrmdraft
|
| Class | errata-ptf
|
| Arrival-Date | Dec 09 2003
|
| Originator | Charles Dawson
|
| Release |
|
| Environment |
|
| Description |
What happens when someone call vpi_put_userdata() then there is a save/restart, then calls vpi_get_userdata()? Should that return NULL? |
| Fix |
After the last paragraph of both sections, add the following paragraph: After a restart or a reset, subsequent calls to vpi_get_userdata() shall return NULL. It is the application's responsibility to save the data during a save using vpi_put_data() and to then retrieve it using vpi_get_data(). The user data field can be setup again during or after callbacks of type cbEndOfRestart or cbEndOfReset. |
| Audit-Trail |
Fix replaced by etf@boyd.com on Mon Dec 15 12:44:21 2003 After the last paragraph of both sections, add the following paragraph: After a restart or a reset, subsequent calls to vpi_get_userdata() will return NULL. It is the application's responsibility to save the data during a save using vpi_put_data() and to then retrieve it using vpi_get_data(). The user data field can be setup again during or after callbacks of type cbEndOfRestart or cbEndOfReset. Fix replaced by etf@boyd.com on Wed Feb 25 14:46:15 2004 After the last paragraph of both sections, add the following paragraph: After a restart or a reset, subsequent calls to vpi_get_userdata() shall return NULL. It is the application's responsibility to save the data during a save using vpi_put_data() and to then retrieve it using vpi_get_data(). The user data field can be setup again during or after callbacks of type cbEndOfRestart or cbEndOfReset. |
| Unformatted |
|
Hosted by Boyd Technology