Yeah, I didn't get the email via the mailing list either. Thanks for the test case, I'll look at it tonight.
Cheers. On Mon, Oct 26, 2009 at 12:30 PM, Josh Gold <josh.g...@xilinx.com> wrote: > Hi Suraj, > > I'm not sure if this email got through since I didn't get a response on > the group. I'm resending it just in case. > > Thanks again! > > -Josh > > -----Original Message----- > From: Josh Gold > Sent: Friday, October 23, 2009 11:26 AM > To: 'ruby-vpi-discuss@rubyforge.org' > Subject: RE: Ruby-VPI - VCS Core Dump iterating for DefParams > > Hi Suraj, > > Thanks for taking a look at this when you have time. I appreciate it. > > Thanks again for making such as great tool as well. > > I've attached an example testcase in the email. > > Let me know if you need anything else. > > Thanks, > -Josh > > -----Original Message----- > From: ruby-vpi-discuss-boun...@rubyforge.org > [mailto:ruby-vpi-discuss-boun...@rubyforge.org] On Behalf Of Suraj > Kurapati > Sent: Tuesday, October 20, 2009 9:37 PM > To: ruby-vpi-discuss@rubyforge.org > Subject: Re: Ruby-VPI - VCS Core Dump iterating for DefParams > > On Tue, Oct 20, 2009 at 3:56 PM, Josh Gold <jo...@xilinx.com> wrote: >> Every interface in the vpiModule can be accessed correctly >> without any issues. > > Glad to hear this. > >> The only issue occurs when trying to read the >> vpiDepParam objects. The error is a core dump in VCS. This issue > seems to >> be regardless to version as VCS fails on both 2006.06-sp1 and 2009.06. > I am >> using ruby-vpi version 21.1.0 as well. >> >> The core dump occures on the following code section: >> >> defparamIterater = vpi_iterate(vpiDefParam, designHandle) >> while(defParamHandle = vpi_scan(defparamIterater)) >> p defParamHandle >> end >> >> The error that VCS reports before the stack traces are dumped is: >> >> Internal error in tool's source file "../vir/vir.cc" line 311. >> Please send these messages to vcs_supp...@synopsys.com. > > Try setting the CFLAGS_EXTRA or the CFLAGS environment variable before > installing Ruby-VPI and you should be able to inspect the core dump > with GDB: > > $ export CFLAGS_EXTRA='-g -DDEBUG' > $ gem install ruby-vpi # will reinstall it > $ rake vcs ... # run your test > (core dump) > $ gdb core `which vcs` > (gdb) bt full # print stack trace > >> Again, this only occurs when trying to view design defparams. Has > anyone >> seen this error before? I was hoping this was something someone has > seen >> before because its hard to imagine that there is a global problem > trying to >> view defparams. > > I haven't tried doing this before and the issue hasn't been raised on > this mailing list so far. > > If you can provide a sample Verilog file that enables the Ruby code > you posted, I can run it against other simulators for comparison. > > Otherwise, please wait for a few days while I regain my strength. I'm > overloaded at work and don't have much energy for tinkering at the > moment. > > Cheers. > > > > This email and any attachments are intended for the sole use of the named > recipient(s) and contain(s) confidential information that may be proprietary, > privileged or copyrighted under applicable law. If you are not the intended > recipient, do not read, copy, or forward this email message or any > attachments. Delete this email message and any attachments immediately. > >
