readlink for files that seem to be linked... #870
Replies: 3 comments 1 reply
-
|
Can include the actual error you're seeing? |
Beta Was this translation helpful? Give feedback.
-
|
I see error: <full path to file>: no such file or directory. I dont see anything else. If I do a vim it just works. Note that the <full path to file> is of the form /mnt/verif/collateral/shared_collateral/../spec_utils/packages/shared.sv Seems like somehow it's not getting resolved properly. Would you be able to suggest how to debug this easily? It's probably in the sourcemanager/SourceLoader somewhere and after you restructured the library a few months ago to add the library mappings, I kind of lost track of how it was doing things... -:) That's why I thought I'd reach out and ask for ideas... Thank you for the wonderful work you do. |
Beta Was this translation helpful? Give feedback.
-
|
The file reading code is in OS.cpp. A simple test on my end works fine with symbolic links. Can you provide a set of steps that reproduce the problem on a standard linux machine? |
Beta Was this translation helpful? Give feedback.
-
|
Mike:
I’m actually working through GDB trying to find the exact fail point. Please grant me a little time to see if I can come up with something that is reproducible For you to look at. As soon as I can reduce this, we should be able to get to the bottom of it.
From: Michael Popoloski ***@***.***>
Date: Saturday, January 20, 2024 at 1:16 PM
To: MikePopoloski/slang ***@***.***>
Cc: Practical-UVM-Step-By-Step ***@***.***>, Author ***@***.***>
Subject: Re: [MikePopoloski/slang] readlink for files that seem to be linked... (Discussion #870)
The file reading code is in OS.cpp. A simple test on my end works fine with symbolic links. Can you provide a set of steps that reproduce the problem on a standard linux machine?
—
Reply to this email directly, view it on GitHub<#870 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEV2OQ33CTVBEAQFAXJYNW3YPQX4LAVCNFSM6AAAAABBXSHGDGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DCOJTGY2TQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Mike:
I Was testing slang against designs where some of the source code was in a soft link off an different NFS server.
I found that slang was complaining that it couldnt open the file and couldnt find it. Error'd out.
None of the usual vendors had this issue. I dont know if this is unique to the way the threading is done in the SourceLoader.
an
lsof the directory shows the file. I was wondering if you could add an API or something that would help us use readlink or some such other mechansim to make this fail-safe via a command line switch or something?Just thought I'd bring it up with you so that you're aware of it.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions