You might want to try running that app under dbx and using the run-time memory checker to see if you can spot any errors:
dbx qlsc (dbx) dbxenv rtc_auto_continue on (dbx) dbxenv error_log_file_name /your/log/file (dbx) check -all -frames 16 (dbx) run list -a wmc -q 8 (That's from memory, so if it doesn't work, you'll have to RTM. And I also just pulled the app name and args from your pstack output - if the qlsc process is started by a parent, and expects certain envvals or files to be populated, just running it from dbx may not work. If that's so, you may have to run it under bcheck: rename qlsc to qlsc.exe or similar, then create a script called qlsc in the original location that does something like "exec /opt/SUNWspro/bin/bcheck -all -o /your/log/file -q `dirname $0`/qlsc.exe $*".) FWIW, it looks like the app is trying to access a shared memory segment after it detaches it. What does a pmap of the core file look like? You might get better support were you to send the link to this discussion to some marketing or management person at the vendor. This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
