Seems a stack problem.  I don't have an OS X box to validate my guess.  I've
made a Google search with the keywords: EXC_BAD_ACCESS stack "os x"

Perhaps the following reply [1] might help...

  How big are they? You're probably running into the default stack size 
  limit, which is 512 KB. Try `unlimit stacksize` in your shell before 
  running, which will give you 65536 KB per stack.

[1] http://zerowing.idsoftware.com/archives/gtkrad-macos/2003-January/000453.html

Sridhar & Recai,

Thanks to both of you for the rapid and effective advice.  Fixing the limit corrected my problem.  
I think I last got tripped up this way 10 years ago...

I suppose that the advice to increase Mac OS X's default stacksize limit might make a fine entry 
in the FAQ or README file.

Thanks again,
Joe 

> I suppose that the advice to increase Mac OS X's default stacksize limit
> might make a fine entry in the FAQ or README file.

I added a note in the installation instructions. 
(http://midas.psi.ch/elog/adminguide.html)

- Stefan

Return-Path: 
Received: from ligo.phys.lsu.edu ([unix socket])
	by ligo.phys.lsu.edu (Cyrus v2.1.13) with LMTP; Wed, 28 Jan 2004 16:27:03 -0600
X-Sieve: CMU Sieve 2.2
Received: from ligo.phys.lsu.edu (ligo.phys.lsu.edu [130.39.181.231])
	by ligo.phys.lsu.edu (Postfix) with SMTP
	id 5E12A788D1; Wed, 28 Jan 2004 16:27:03 -0600 (CST)
To: ELOG@ligo.phys.lsu.edu, user@ligo.phys.lsu.edu
From: elog@ligo.phys.lsu.edu
Subject: New playground elog entry
X-Mailer: Elog, Version 2.3.9
X-Elog-URL: http://ligo.phys.lsu.edu:8080/playground/13
X-Elog-submit-type: web|elog
Date: Wed, 28 Jan 2004 22:27:03 +52182819
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-Id: <20040128222703.5E12A788D1@ligo.phys.lsu.edu>

A new entry has been submitted on ligo.phys.lsu.edu

Logbook             : playground
Author              : Joseph Giaime
Type                : Other
Category            : Other
Subject             : yet another test

Logbook URL         : http://ligo.phys.lsu.edu:8080/playground/13

> Instead of something like "Date: Wed, 28 Jan 2004 14:46:16 -0600", the
> "-0600" is replaced by a large number that doesn't correspond with anything
> I can figure out.  This is the sort of thing that does no real harm, but the
> notebook users keep complaining. 

This is caused by the elogd program itself. To produce the "-0600", it uses the 
variable "timezone", which is defined as difference in seconds between local time 
and coordinated universl time. This works find under Windows, Linux, FreeBSD, but 
apparently not under MacOSX. Although this variable is defined, it's unassigned. 

The code where this is used is in sendmail(), at the lines

   time(&now);
   ts = localtime(&now);
   strftime(buf, sizeof(buf), "%a, %d %b %Y %H:%M:%S", ts);
   offset = (-(int) timezone);
   if (ts->tm_isdst)
      offset += 3600;

The current localtime gets written into "buf", then the timzone offset gets 
corrected by the daylight savings time, then the offset is used to produce the 
"-0600".

So if anybody being familiar with MacOSX has some idea, please let me know.

- Stefan

/usr/bin/install -m 0755 -d /usr/local/bin /usr/local/sbin /usr/local/man/man1/ /usr/local/man/man8/
/usr/bin/install -m 0755 -o bin -g bin elog elconv /usr/local/bin
install: bin: Invalid argument
make: *** [install] Error 67

ifeq ($(OSTYPE),darwin)
CC = cc
endif

diff Makefile.darwin Makefile.origin
====================================
24,25d23
< BINOWNER = bin
< BINGROUP = bin
30,31d27
< OSTYPE = $(shell uname)
<
40,43d35
< ifeq ($(OSTYPE),Darwin)
< OSTYPE=darwin
< endif
<
46,47d37
< BINOWNER = root
< BINGROUP = admin
89,90c79,80
<       $(INSTALL) -m 0755 -o ${BINOWNER} -g ${BINGROUP} elog elconv $(DESTDIR)
<       $(INSTALL) -m 0755 -o ${BINOWNER} -g ${BINGROUP} elogd $(SDESTDIR)
---
>       $(INSTALL) -m 0755 -o bin -g bin elog elconv $(DESTDIR)
>       $(INSTALL) -m 0755 -o bin -g bin elogd $(SDESTDIR)