dsc@osteocyber.ortho.hmc.psu.edu (david s. channin) (03/11/91)
I've written an Xview app using Guide1.1 on a Sparc2 (Sunos 4.1.1). It has several scrolling lists in a couple of panels. After updating the scrolling lists a handful of times, I get: Xview warning: Ivalid Object 0x<HEx Object Id> : embedding seal incorrect Needless to say I am having great difficulties debugging this. I define my own error proc in xv_init but when the program gets to my routine, the object number is already invalid so I cant use Xv_pkg to find out which object it is. I have put XFlushes throughout the code to make sure it breaks relatively soon after the error but that hasn't seemed to help., I have remade all the Guide files, recompiled and relinked all my files but I still get this message. Any ideas? Thanks. David S. Channin dsc@osteocyber.ortho.hmc.psu.edu Department of Radiology Hershey Medical Center Hershey, PA 17033
tomj@snowking.Eng.Sun.COM (Tom Jacobs) (03/12/91)
In article <2!cGc=5&@cs.psu.edu>, dsc@osteocyber.ortho.hmc.psu.edu (david s. channin) writes: |> I've written an Xview app using Guide1.1 on a Sparc2 (Sunos 4.1.1). |> It has several scrolling lists in a couple of panels. After updating the |> scrolling lists a handful of times, I get: |> |> Xview warning: Ivalid Object 0x<HEx Object Id> : embedding seal incorrect |> |> Needless to say I am having great difficulties debugging this. I define |> my own error proc in xv_init but when the program gets to my routine, the |> object number is already invalid so I cant use Xv_pkg to find out which |> object it is. I have put XFlushes throughout the code to make sure it breaks |> relatively soon after the error but that hasn't seemed to help., I have |> remade all the Guide files, recompiled and relinked all my files but I still |> get this message. Any ideas? |> |> Thanks. |> |> David S. Channin |> dsc@osteocyber.ortho.hmc.psu.edu |> |> Department of Radiology |> Hershey Medical Center |> Hershey, PA 17033 You'll get this warning whenever a non-XView object handle is passed handed to a generic xv_*() function. Sometimes these errors occur when your code uses a value returned from xv_create/get/find in another xv_*() call without first checking to see if the value is either NULL or XV_ERROR. To find this place where the bad object value is being passed, you'll need to place a break point at the entry point to xv_error() and then look at the stack trace. --- Tom Jacobs ARPA: tomj@Eng.Sun.com Sun Microsystems, Inc. UUCP: sun!tomj