rodCreateHandle - how to prevent warnings?

S

Sylvio Triebel

Guest
Hi,
I'm extensively using rodCreateHandle in my layout generators...
(icfb sub-version 5.10.41.500.2.23)

It works fine except that I get a lot of warnings which slow down the whole framework:
*WARNING* dbOpenBag: Failed to open prop. bag for 'cdsDefTechLib' in 'r' mode, file not found

This is only for ?type "point" handles, ?type "float" works without warning....

The layout generator generates the layout in a library which is attached to a valid techLib.

Is there something special to look at?
From where could rodCreateHandle get the string "cdsDefTechLib"?

Both,
techGetTechFile(rodId~>cvId)~>libName
techGetTechFile(rodId~>cvId)~>fileName
will return expected values...

Thanks for any feedback,
Sylvio


P.S.: my current workaround:

oldwoport = poport
devNull = outfile("/dev/null")
woport = devNull ;suppress all warnings

create handles .....


close(devNull)
woport = oldwoport


Perhaps there is also a better way to inactivate outputs...
 
On Fri, 14 Jul 2006 13:12:37 +0200, Sylvio Triebel <Sylvio.Triebel@nospam.com>
wrote:

Hi,
I'm extensively using rodCreateHandle in my layout generators...
(icfb sub-version 5.10.41.500.2.23)

It works fine except that I get a lot of warnings which slow down the whole framework:
*WARNING* dbOpenBag: Failed to open prop. bag for 'cdsDefTechLib' in 'r' mode, file not found

This is only for ?type "point" handles, ?type "float" works without warning....

The layout generator generates the layout in a library which is attached to a valid techLib.

Is there something special to look at?
From where could rodCreateHandle get the string "cdsDefTechLib"?

Both,
techGetTechFile(rodId~>cvId)~>libName
techGetTechFile(rodId~>cvId)~>fileName
will return expected values...

Thanks for any feedback,
Sylvio


P.S.: my current workaround:

oldwoport = poport
devNull = outfile("/dev/null")
woport = devNull ;suppress all warnings

create handles .....


close(devNull)
woport = oldwoport


Perhaps there is also a better way to inactivate outputs...
Click to expand...
I don't see why rodCreateHandle should be accessing any property bags. You don't
show the code that is causing this - it might reveal something.

Perhaps the warning isn't coming from the place in the code that you think it
is? Remember that warnings are deferred until the next warning, or until
getWarn() is called, to get you an opportunity to swallow warnings using
getWarn().

Andrew.
--
Andrew Beckett
Principal European Technology Leader
Cadence Design Systems, UK.
 
Andrew Beckett wrote:
On Fri, 14 Jul 2006 13:12:37 +0200, Sylvio Triebel <Sylvio.Triebel@nospam.com
wrote:


Hi,
I'm extensively using rodCreateHandle in my layout generators...
(icfb sub-version 5.10.41.500.2.23)

It works fine except that I get a lot of warnings which slow down the whole framework:
*WARNING* dbOpenBag: Failed to open prop. bag for 'cdsDefTechLib' in 'r' mode, file not found

This is only for ?type "point" handles, ?type "float" works without warning....

The layout generator generates the layout in a library which is attached to a valid techLib.

Is there something special to look at?
From where could rodCreateHandle get the string "cdsDefTechLib"?

Both,
techGetTechFile(rodId~>cvId)~>libName
techGetTechFile(rodId~>cvId)~>fileName
will return expected values...

Thanks for any feedback,
Sylvio


P.S.: my current workaround:

oldwoport = poport
devNull = outfile("/dev/null")
woport = devNull ;suppress all warnings

create handles .....


close(devNull)
woport = oldwoport


Perhaps there is also a better way to inactivate outputs...


I don't see why rodCreateHandle should be accessing any property bags. You don't
show the code that is causing this - it might reveal something.

Perhaps the warning isn't coming from the place in the code that you think it
is? Remember that warnings are deferred until the next warning, or until
getWarn() is called, to get you an opportunity to swallow warnings using
getWarn().

Andrew.
--
Andrew Beckett
Principal European Technology Leader
Cadence Design Systems, UK.
Check to see if the "prop.xx" file exists in the target library. If not,
Click to expand...
create an empty one should be good enough to avoid to get those warning
messages. I noticed that this only applies to icfb 5.0 and above.
 
Hi,
thanks for the late answer...

The target library has always a prop.xx file (the property techLibName...)
....only the cdsDefTechLib has no prop.xx file.

By the way, it seems now difficult to reproduce the error.
At the moment I can't see the warnings if I disable the woport re-direction.
Perhaps it is related with the structure of the techfile??
We get frequently new versions. The icfb version is still the same.

I'm only sure that the warning was related with rodCreateHandle.
But I don't have time to investigate more time on this issue.

Regards,
Sylvio

PS: here some code... but I don't think that it will reveal something.

I located the occurence of the warning with "printf debugging".
To use the same stream buffer I used fprintf(woport "mark 1\n") ...

fprintf(woport "mark 1\n")
rodId = rodGetObj("" currentCellView)

rodCreateHandle( ?rodObj rodId ?type "float"
?name strcat(glayer->name "_width")
?value x1-x0 )
rodCreateHandle( ?rodObj rodId ?type "float"
?name strcat(glayer->name "_height")
?value y1-y0 )

;;the following lines create the warnings
fprintf(woport "mark 2\n")
rodCreateHandle( ?rodObj rodId ?type "point"
?name strcat(glayer->name "_lowerLeft")
?value x0:y0 )
rodCreateHandle( ?rodObj rodId ?type "point"
?name strcat(glayer->name "_lowerRight")
?value x1:y0 )
rodCreateHandle( ?rodObj rodId ?type "point"
?name strcat(glayer->name "_upperLeft")
?value x0:y1 )
rodCreateHandle( ?rodObj rodId ?type "point"
?name strcat(glayer->name "_upperRight")
?value x1:y1 )

fprintf(woport "mark 3\n")

=>
mark 1
mark 2
*WARNING* dbOpenBag: Failed to open prop. bag for 'cdsDefTechLib' in 'r' mode, file not found
*WARNING* dbOpenBag: Failed to open prop. bag for 'cdsDefTechLib' in 'r' mode, file not found
*WARNING* dbOpenBag: Failed to open prop. bag for 'cdsDefTechLib' in 'r' mode, file not found
*WARNING* dbOpenBag: Failed to open prop. bag for 'cdsDefTechLib' in 'r' mode, file not found
mark 3

drc_98 wrote:
Andrew Beckett wrote:

On Fri, 14 Jul 2006 13:12:37 +0200, Sylvio Triebel
Sylvio.Triebel@nospam.com
wrote:


Hi,
I'm extensively using rodCreateHandle in my layout generators...
(icfb sub-version 5.10.41.500.2.23)

It works fine except that I get a lot of warnings which slow down the
whole framework:
*WARNING* dbOpenBag: Failed to open prop. bag for 'cdsDefTechLib' in
'r' mode, file not found

This is only for ?type "point" handles, ?type "float" works without
warning....

The layout generator generates the layout in a library which is
attached to a valid techLib.

Is there something special to look at?
From where could rodCreateHandle get the string "cdsDefTechLib"?

Both,
techGetTechFile(rodId~>cvId)~>libName
techGetTechFile(rodId~>cvId)~>fileName
will return expected values...

Thanks for any feedback,
Sylvio


P.S.: my current workaround:

oldwoport = poport
devNull = outfile("/dev/null")
woport = devNull ;suppress all warnings

create handles .....


close(devNull)
woport = oldwoport


Perhaps there is also a better way to inactivate outputs...



I don't see why rodCreateHandle should be accessing any property bags.
You don't
show the code that is causing this - it might reveal something.

Perhaps the warning isn't coming from the place in the code that you
think it
is? Remember that warnings are deferred until the next warning, or until
getWarn() is called, to get you an opportunity to swallow warnings using
getWarn().

Andrew.
--
Andrew Beckett
Principal European Technology Leader
Cadence Design Systems, UK.

Check to see if the "prop.xx" file exists in the target library. If not,
create an empty one should be good enough to avoid to get those warning
messages. I noticed that this only applies to icfb 5.0 and above.
Click to expand...
 
You must log in or register to reply here.

Welcome to EDABoard.com

Sponsor

Back
Top