# Debugging VIP's API calls

**URL:** <https://verificationacademy.com/forums/t/debugging-vips-api-calls/51709>\
**Category:** SystemVerilog\
**Tags:** SystemVerilog, Polymorphism\
**Created:** [July 29, 2026, 1:28pm UTC](https://verificationacademy.com/forums/t/debugging-vips-api-calls/51709 "2026-07-29T13:28:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bhosaleakash00](https://verificationacademy.com/forums/letter_avatar_proxy/v4/letter/b/ac91a4/32.png) [@bhosaleakash00](https://verificationacademy.com/forums/u/bhosaleakash00)\
**Post date:** [July 29, 2026, 1:28pm UTC](https://verificationacademy.com/forums/t/debugging-vips-api-calls/51709/1 "2026-07-29T13:28:18Z")

</div>

Hi Forum,

As a newbie I was trying following code on [edaplayground](https://www.edaplayground.com/x/gjHX)

Class `send_txn1` inherits non-virtual function `activate` and overrides virtual function `do_activate`

(1) Why does the overridden task `do_activate` get called and not the `do_activate` API in base class ?

(2) Wouldn’t the call to `activate` call the task defined in base class ?

(3) What does inheritance actually mean ? I understand that extended classes have access to inherited APIs / properties

Would the `activate` task implicitly be written as part of extended class ? i.e Is it equivalent to re-write `activate` in extended class ?

Thanks

---

<div class="post-metadata">

**Author:** ![dave\_59](https://verificationacademy.com/forums/user_avatar/verificationacademy.com/dave_59/32/4499_2.png) [@dave\_59](https://verificationacademy.com/forums/u/dave_59)\
**Post date:** [August 3, 2026, 4:18pm UTC](https://verificationacademy.com/forums/t/debugging-vips-api-calls/51709/2 "2026-08-03T16:18:08Z")

</div>

Before attempting to use the UVM, you should study SystemVerilog object-oriented programming. Many resources are available, including those provided by the [Verification Academy](https://verificationacademy.com/topics/systemverilog/systemverilog-oop-for-uvm-verification/).

In SystemVerilog, a call to a virtual method works by examining the runtime type of the object that makes the call, rather than just the type used in the variable declaration, and it calls the most derived method available for that object.
