dbx panic

Hi,

While debugging core on Solaris 8, i m getting following error..

dbx: panic: "Prog::primary_LO no primary LO!"(): Assertion (lo != NULL) failed - "prog.cc":867

Can anybody figure out what is the reason for the error?

Any pointer regarding would be appreciated.

thanks,

Sagar Shah

[326 byte] By [Sagar_Shah] at [2007-11-26 10:01:13]
# 1
Sagar,you've probably hit a dbx bug. Would you please file it through http://bugs.sun.com/services/bugreport/index.jsp ?Thanks,Boris
Boris_Ivanovsky at 2007-7-7 1:31:25 > top of Java-index,Development Tools,Solaris and Linux Development Tools...
# 2
Which version of dbx are you using?The most common problem with core files is whenthey are truncated by the OS when they are written to disk.Newer versions of dbx should diagnose this with a warning.
ChrisQuenelle at 2007-7-7 1:31:25 > top of Java-index,Development Tools,Solaris and Linux Development Tools...
# 3
Also (a wild guess) try specifying the program name, if you haven't done this already. That is, start dbx as$ dbx prog coreinstead of$ dbx - coreNot sure if it can help, but wo knows...
MaximKartashev at 2007-7-7 1:31:25 > top of Java-index,Development Tools,Solaris and Linux Development Tools...
# 4
thnx Chris,I am using dbx 6.2After working on the issue for about a month, unfortunetly, still i am not able to solve this issue.can anybody provide some pointer?Regards,Sagar Shah
Sagar_Shah at 2007-7-7 1:31:25 > top of Java-index,Development Tools,Solaris and Linux Development Tools...
# 5

6.2 is rather old version (about 5 years old) so I suggest upgrading to one of the latest Sun Studio version -- either Sun Studio 11 (latest release that includes dbx 7.5) or maybe Sun Studio Express (one of the latest builds). Both are available for download for free at

http://developers.sun.com/prodtech/cc/downloads/index.jsp

and

http://developers.sun.com/prodtech/cc/downloads/express.jsp

MaximKartashev at 2007-7-7 1:31:25 > top of Java-index,Development Tools,Solaris and Linux Development Tools...
# 6
Forgot to mention that if this problem persists after the upgrade and you can provide me with the core file, we will work on this issue.
MaximKartashev at 2007-7-7 1:31:25 > top of Java-index,Development Tools,Solaris and Linux Development Tools...
# 7

Thanks very much for your prompt reply. the error has been disappeared, but now, I am not getting the stack trace of the thread which is causing core dump. dbx displays the warning that thread related will not be available. It is not able to initialize the thread library.

Here I paste the warnings which dbx throws

A loadobject was found with an unexpected checksum value.

See `help core mismatch' for details, and run `proc -map'

to see what checksum values were expected and found.

dbx: warning: Some symbolic information might be incorrect.

dbx: warning: could not initialize thread debugging library -- program is not linked with libthread

dbx: warning: thread related commands will not be available

dbx: warning: see `help lwp', `help lwps' and `help where'

Could you please provide some pointer regarding how to deal with this situation.

Thanks once again.

Sagar_Shah at 2007-7-7 1:31:25 > top of Java-index,Development Tools,Solaris and Linux Development Tools...
# 8
Are you running dbx on the same machine where the core dump happened? That is the most common cause of a "mismatched core file".--chris
ChrisQuenelle at 2007-7-7 1:31:25 > top of Java-index,Development Tools,Solaris and Linux Development Tools...
# 9
> Could you please provide some pointer regarding how to deal with this situation.The best source of information is `help core mismatch', it explains the nature of the problem; other than that, only google might know...
MaximKartashev at 2007-7-7 1:31:25 > top of Java-index,Development Tools,Solaris and Linux Development Tools...