[Orca-users] SE Toolkit 3.4 - segmentation fault
Dmitry Berezin
dberezin at surfside.rutgers.edu
Thu Mar 30 07:04:16 PST 2006
Here is the note from sunfreeware; substitute the version of gcc and it
should fix your compiler problem:
**********************************
Note that this version of gcc was created on build 60 of Solaris 10. If you
are using a higher version, you will need to redo some of the header files.
This is done by doing the following steps:
cd /usr/local/lib/gcc-lib/sparc-sun-solaris2.10/3.3.2/install-tools/
Put the line SHELL=/bin/sh on the first line of the mkheaders.conf
file. Then run
./mkheaders
This will correct some files and make the build 60 gcc usable on
higher builds. I have tested this on build 72 and it works fine.
**********************************
-Dmitry.
> -----Original Message-----
> From: orca-users-bounces+dberezin=acs.rutgers.edu at orcaware.com
> [mailto:orca-users-bounces+dberezin=acs.rutgers.edu at orcaware.com] On
> Behalf Of Stefan.Schuster at dzi.lu
> Sent: Thursday, March 30, 2006 2:51 AM
> To: mike.normandin at credit-suisse.com; dragon at raytheon.com
> Cc: orca-users at orcaware.com
> Subject: AW: [Orca-users] SE Toolkit 3.4 - segmentation fault
>
> Hi,
>
> thanks for the information. Recompiling se on a Solaris 10 workstation was
> no problem. I put it
> on the Sun Cluster Node, but it didn´t work. Recompiling (gcc 3.4.3) on
> the Clusternode itself failed
> with the following error messages:
>
> --------------------------------------------------------------------------
> -------------
> echo '#define NOW "\c' > version.c
> echo `/bin/date '+%I:%M %p %D'`\\c >> version.c
> echo '"' >> version.c
> cat version >> version.c
> yacc -dl se.y
> mv y.tab.c se.c
> gcc -g -D`uname -p` -c se.c
> gcc -g -D`uname -p` -c avl.c
> gcc -g -D`uname -p` -c debug.c
> gcc -g -D`uname -p` -c extern.c
> gcc -g -D`uname -p` -c funcs.c
> gcc -g -D`uname -p` -c generate.c
> gcc -g -D`uname -p` -c kstat.c
> In file included from /usr/include/sys/signal.h:34,
> from /usr/include/sys/klwp.h:14,
> from /usr/include/sys/thread.h:13,
> from /usr/include/sys/fs/cachefs_fs.h:16,
> from kstat.c:11:
> /usr/include/sys/siginfo.h:259: error: parse error before "ctid_t"
> /usr/include/sys/siginfo.h:292: error: parse error before '}' token
> /usr/include/sys/siginfo.h:294: error: parse error before '}' token
> /usr/include/sys/siginfo.h:390: error: parse error before "ctid_t"
> /usr/include/sys/siginfo.h:392: error: conflicting types for `__proc'
> /usr/include/sys/siginfo.h:261: error: previous declaration of `__proc'
> /usr/include/sys/siginfo.h:398: error: conflicting types for `__fault'
> /usr/include/sys/siginfo.h:267: error: previous declaration of `__fault'
> /usr/include/sys/siginfo.h:404: error: conflicting types for `__file'
> /usr/include/sys/siginfo.h:273: error: previous declaration of `__file'
> /usr/include/sys/siginfo.h:420: error: conflicting types for `__prof'
> /usr/include/sys/siginfo.h:287: error: previous declaration of `__prof'
> /usr/include/sys/siginfo.h:424: error: conflicting types for `__rctl'
> /usr/include/sys/siginfo.h:291: error: previous declaration of `__rctl'
> /usr/include/sys/siginfo.h:426: error: parse error before '}' token
> /usr/include/sys/siginfo.h:428: error: parse error before '}' token
> /usr/include/sys/siginfo.h:432: error: parse error before "k_siginfo_t"
> /usr/include/sys/siginfo.h:437: error: parse error before '}' token
> In file included from /usr/include/sys/klwp.h:14,
> from /usr/include/sys/thread.h:13,
> from /usr/include/sys/fs/cachefs_fs.h:16,
> from kstat.c:11:
> /usr/include/sys/signal.h:85: error: parse error before "siginfo_t"
> In file included from /usr/include/sys/klwp.h:21,
> from /usr/include/sys/thread.h:13,
> from /usr/include/sys/fs/cachefs_fs.h:16,
> from kstat.c:11:
> /usr/include/sys/contract.h:58: error: parse error before "ctid_t"
> /usr/include/sys/contract.h:68: error: parse error before '}' token
> /usr/include/sys/contract.h:71: error: parse error before "ctid_t"
> /usr/include/sys/contract.h:86: error: parse error before '}' token
> In file included from /usr/include/sys/thread.h:13,
> from /usr/include/sys/fs/cachefs_fs.h:16,
> from kstat.c:11:
> /usr/include/sys/klwp.h:96: error: parse error before "k_siginfo_t"
> /usr/include/sys/klwp.h:171: error: parse error before '}' token
> In file included from /usr/include/sys/fs/cachefs_fs.h:16,
> from kstat.c:11:
> /usr/include/sys/thread.h:145: error: parse error before "klwp_t"
> /usr/include/sys/thread.h:320: error: parse error before '}' token
> In file included from /usr/include/sys/systm.h:20,
> from /usr/include/sys/fs/cachefs_fs.h:20,
> from kstat.c:11:
> /usr/include/sys/proc.h:62: error: parse error before "kthread_t"
> /usr/include/sys/proc.h:68: error: parse error before '}' token
> /usr/include/sys/proc.h:183: error: parse error before "kthread_t"
> /usr/include/sys/proc.h:200: error: parse error before '*' token
> /usr/include/sys/proc.h:297: error: parse error before '*' token
> /usr/include/sys/proc.h:310: error: parse error before '}' token
> In file included from /usr/include/nfs/nfs_clnt.h:44,
> from kstat.c:14:
> /usr/include/nfs/rnode.h:163: error: parse error before "kthread_t"
> /usr/include/nfs/rnode.h:166: error: parse error before '}' token
> In file included from kstat.c:14:
> /usr/include/nfs/nfs_clnt.h:166: error: parse error before "kthread_t"
> /usr/include/nfs/nfs_clnt.h:169: error: parse error before '}' token
> /usr/include/nfs/nfs_clnt.h:183: error: parse error before
> "nfs_delmapcall_t"
> /usr/include/nfs/nfs_clnt.h:346: error: parse error before "kthread_t"
> /usr/include/nfs/nfs_clnt.h:387: error: parse error before '}' token
> *** Error code 1
> make: Fatal error: Command failed for target `kstat.o'
>
> --------------------------------------------------------------------------
> ----------------
> But I think you are right, there is a problem with diskinfo.se. Any
> idea??????
>
> Best,
> Stefan
>
> -----Ursprüngliche Nachricht-----
> Von: orca-users-bounces+stefan.schuster=dzi.lu at orcaware.com [mailto:orca-
> users-bounces+stefan.schuster=dzi.lu at orcaware.com] Im Auftrag von
> Normandin, Mike
> Gesendet: Mittwoch, 29. März 2006 23:13
> An: Schuster, Stefan; dragon at raytheon.com
> Cc: orca-users at orcaware.com
> Betreff: RE: [Orca-users] SE Toolkit 3.4 - segmentation fault
>
>
>
> I was receiving segmentation faults on se 3.4 as well on solaris 10
> with certain external SAN disks attached. It was happening when
> diskinfo.se was walking through the device tree. I recompiled se on
> Solaris 10 and the problem went away.
>
> Using the debug option on se:
>
> refresh$(sderr(STRUCTURE))
> short_name = sderr.name$<sd287,err> strtok(short_name<sd287,err>, <,>) if
> (short_name<sd287> == name<sd287>)
> break;
> return sderr(STRUCTURE);
> count++;
> ld = readdir(dirp<18446744071530611328>)
> if (count<32> == GLOBAL_diskinfo_size<266>)
> dp = *((dirent_t *) ld<18446744071530634992>)
>
>
> truss output
>
> 26620: ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1388
> 26620: ioctl(4, KSTAT_IOC_READ, "sd30,err") = 1388
> 26620: ioctl(4, KSTAT_IOC_CHAIN_ID, 0x00000000) = 1388
> 26620: ioctl(4, KSTAT_IOC_READ, "sd287,err") = 1388
> 26620: Incurred fault #6, FLTBOUNDS %pc = 0xFFFFFFFF7DE0092C
> 26620: siginfo: SIGSEGV SEGV_MAPERR addr=0xFFFFFFFF7ED06000
> 26620: Received signal #11, SIGSEGV [default]
> 26620: siginfo: SIGSEGV SEGV_MAPERR addr=0xFFFFFFFF7ED06000
> 26619: waitid(P_PID, 26620, 0xFFBFFA98, WEXITED|WTRAPPED|WNOWAIT) = 0
> 26619: ioctl(0, TIOCGPGRP, 0xFFBFFAB4) = 0
> 26619: ioctl(0, TCGETS, 0x00039178) = 0
> 26619: waitid(P_PID, 26620, 0xFFBFFA98, WEXITED|WTRAPPED) = 0
> 26619: write(2, " S e g m e n t a t i o n".., 19) = 19
> 26619: brk(0x0003A3F0)
>
>
>
>
>
> = 0
> -----Original Message-----
> From: orca-users-bounces+mike.normandin=csfb.com at orcaware.com
> [mailto:orca-users-bounces+mike.normandin=csfb.com at orcaware.com]On
> Behalf Of Stefan.Schuster at dzi.lu
> Sent: Monday, March 27, 2006 10:51 AM
> To: dragon at raytheon.com
> Cc: orca-users at orcaware.com
> Subject: AW: [Orca-users] SE Toolkit 3.4 - segmentation fault
>
>
> Hi David,
>
> I am using the last snapshot Orca 0.28, but I´ve still the problem.
> Perhaps there is something special with Solaris 10, Sun Cluster 3.1.....I
> did some traces (starting orcallator with truss, and I got some errors
> concerning "kstat". Could there be a problem in orcallator.se???
>
> BR
> Stefan
>
> -----Ursprüngliche Nachricht-----
> Von: David Michaels [mailto:dragon at raytheon.com]
> Gesendet: Freitag, 24. März 2006 19:59
> An: Schuster, Stefan
> Cc: orca-users at orcaware.com
> Betreff: Re: [Orca-users] SE Toolkit 3.4 - segmentation fault
>
>
> Stefan.Schuster at dzi.lu wrote:
> > Helle All,
> >
> > I got a segmetation fault, starting SETool components (monlog,
> > percol,vader, va_monitor).
> >
> > Using: Solaris 10. US IV+ (new 1,5 GHz) CPU, Veritas VxVM 4.1; Sun
> > Cluster 3.1, SE Toolkit 3.4.
> >
> > It´s also not possible to start orcallator (segmentation fault!!), but
> > in SE Toolkit 3.4 it´s not the old problem with "USE_RAW.........".
> >
> > Anybody have an idea to solve this problem???
> >
>
> What rev of orcallator.se are you using and what rev of Orca itself are
> you using?
>
> If you're using Orca 0.27, you need to grab the latest snapshot instead.
>
> If you're using orcallator.se 1.37 or earlier, you need to grab the
> latest snapshot, and extract the orcallator.se from it.
>
> If you're using new stuff, but still seg faulting, that's a new problem,
> and we'll need more info (cut&paste some errors, for example).
>
> --Dragon, nemo omnibus horis sapit
>
>
>
> **********************************************************************
> This message and any attachment are confidential and may be privileged or
> otherwise protected from disclosure.
>
> If you are not the intended recipient, please call or e-mail the sender
> and delete the message and any attachment from your system.
>
> If you are not the intended recipient, you must not copy this message
> or attachment or disclose the contents to any other person.
>
> E-mail transmission cannot be guaranteed to be secure or error-free as
> information could be intercepted, corrupted, lost, destroyed, arrive
> later or incomplete, or contain viruses.
>
> The sender therefore does not accept liability for any errors or
> omissions in the contents of this message which arises as a result of
> e-mail transmission.
>
> If verification is required please request a hard-copy version.This
> message is provided for informational purposes only and should not be
> construed as a solicitation or offer to buy or sell any securities or
> related financial instruments.
> **********************************************************************
>
> _______________________________________________
> Orca-users mailing list
> Orca-users at orcaware.com http://www.orcaware.com/mailman/listinfo/orca-
> users
>
> ==========================================================================
> ====
> Please access the attached hyperlink for an important electronic
> communications disclaimer:
>
> http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
> ==========================================================================
> ====
>
>
> _______________________________________________
> Orca-users mailing list
> Orca-users at orcaware.com http://www.orcaware.com/mailman/listinfo/orca-
> users
>
>
>
> **********************************************************************
> This message and any attachment are confidential and may be privileged or
> otherwise protected from disclosure.
>
> If you are not the intended recipient, please call or e-mail the sender
> and delete the message and any attachment from your system.
>
> If you are not the intended recipient, you must not copy this message
> or attachment or disclose the contents to any other person.
>
> E-mail transmission cannot be guaranteed to be secure or error-free as
> information could be intercepted, corrupted, lost, destroyed, arrive
> later or incomplete, or contain viruses.
>
> The sender therefore does not accept liability for any errors or
> omissions in the contents of this message which arises as a result of
> e-mail transmission.
>
> If verification is required please request a hard-copy version.This
> message is provided for informational purposes only and should not be
> construed as a solicitation or offer to buy or sell any securities or
> related financial instruments.
> **********************************************************************
>
> _______________________________________________
> Orca-users mailing list
> Orca-users at orcaware.com
> http://www.orcaware.com/mailman/listinfo/orca-users
More information about the Orca-users
mailing list