In article <1992Dec31.152754.27251@atinc.uucp>, root@atinc.uucp (Operator) writes:
|> I have created a custom widget which has many resources. I have noticed recently that when setting resources with XtSetArg before calling XtCreateWidget, that the application core dumps in the XtCreateWidget call. I don't know if its a certain order whe|> n setting the resources, and if its the number of resources set, but dbx definitely traces the problem in XtCreateWidget(). Actually _XtCreateWidget, which is called by XtCreateWidget(), with a seg violation at the top of memory.
|>
|> Using XtSetValues seems to work fine.
|>
|> Can anyone shed some light on this for me. I'm wondering if I have a resource conflict. I am thinking that the problem exists when looking at the resource list passed down from the application. My widget code is not called yet, so the resource list migh|> t be clobbering something, maybe. Help before I tracethrought the Intrinsics with the debugger.
The order is not important.
Since Create does not work and SetValues does,
I would suspect that your Initialize method
is faulty.
Some debuggers are not smart enough to tell you where
you really are (accurately) when you have gone through a function
pointer. You might be inside your Initialize procedure
and not know it.
I would recommend putting "printf"'s in your Initialize procedure.
Duplicate resources are not a problem.
The one furthest down in the heirarchy is the one that is used.
