Re: CREATE_PROBE_DISPLAY

[Alex Lancaster]

>>>>> "MG" == Matt Gaston <address@hidden> writes:

MG> Under Solaris 7 (2.7) I have built Swarm from source successfully.

Firstly, we have binary packages for Solaris 2.7.  It's probably worth
your while using those before resorting to a source build - that's why
we build them in the first place!  See the following ftp site for the
packages:

 ftp://ftp.swarm.org/pub/swarm/binaries/solaris-2.7/

The binary packages are all listed on the main download webpage (see
Solaris 2.7):

 http://www.swarm.org/release-swarm.html

MG> Now, I am having a problem somewhere in the CREATE_PROBE_DISPLAY
MG> macro.  The best description of the problem is a segmentation
MG> fault.  

The _best description of the problem_ is a backtrace from `gdb'.  To
merely report a seg fault is just reporting the symptom, not analysing
the cause.

MG> Any ideas where to start?  I thought I would ask the list before I
MG> start editting the code.

If the executable is called `bug' (say).  Go to the application
directory (say simpleObserverBug) and type:

$ gdb .libs/bug core
$ bt

Send the resulting backtrace (`bt' is the abbreviated command name) to
the list.

See also the section in the User Guide on debugging:

http://www.santafe.edu/projects/swarm/swarmdocs/userbook/swarm.tech.sgml.sect1.debug.html

MG> The seg fault occurs even in the simplest examples
MG> (simpleObserverBug2)!

I suspect something wrong in your Swarm build.  Also make sure your
DISPLAY variable is set correctly.

Alex
-- 
Alex Lancaster * address@hidden * www.santafe.edu/~alex * 505 984-8800 x242
Santa Fe Institute (www.santafe.edu) & Swarm Development Group (www.swarm.org)

                  ==================================
   Swarm-Support is for discussion of the technical details of the day
   to day usage of Swarm.  For list administration needs (esp.
   [un]subscribing), please send a message to <address@hidden>
   with "help" in the body of the message.