On Tue, Jun 15, 2010 at 11:14 AM, David Ashley
wrote:
> Any idea why killer.exe would fail with an access denied during a build?
I have an idea, but I haven't investigated. The access denied comes
from not having enough rights to kill the process.
Originally, killer.exe just worked. Then when
Mark -
Any idea why killer.exe would fail with an access denied during a build?
The virtual machine has rxapi installed as a daemon. Should it not be a
daemon on a build machine?
In any case, it does not seem to matter whether or not rxapi is running
or not, the build still completes successfu
Not much use. It's dying somehow in the code for the Deque
instruction while initializing one of the static variables of the
ActivityManager class. At this point, there's not even any of the
ooRexx code that's even been invoked.
Rick
On Tue, Jun 15, 2010 at 12:16 PM, David Ashley
wrote:
> Rick
Oops! Sorry, the last email had an incomplete backtrace. Here is the
complete one.
Program received signal SIGILL, Illegal instruction.
0x0215c4a0 in max (__b=,
__a=) at
/usr/include/c++/4.3/bits/stl_algobase.h:215
215 if (__a < __b)
(gdb) bt
#0 0x0215c4a0 in max (
Rick -
When building ooRexx on SLES 11 (s390x) the rexximage program crashes
with an illegal instruction. Here is the backtrace.
#0 0x0215c4a0 in max (__b=,
__a=) at
/usr/include/c++/4.3/bits/stl_algobase.h:215
#1 std::_Deque_base
>::_M_initialize_map (__b=, __a=)
at /usr/
David,
At SDI we gave up on the Windows schedule system before we ever got started
with it. In lieu of it,
we wrote a simple Rexx script that wakes up every 30 seconds and checks a data
base of scheduled
jobs to see if it has anything to do at the current date/time.
In you situation, you woul
On Tue, Jun 15, 2010 at 9:45 AM, David Ashley
wrote:
> All -
>
> I am close to getting the new Build Machine up an running. There are
> still a few problems to correct but I am close.
>
> 1. There was a bug in the crontab entry which prevented the fedora 13
> i386 build from ever running. That was
All -
I am close to getting the new Build Machine up an running. There are
still a few problems to correct but I am close.
1. There was a bug in the crontab entry which prevented the fedora 13
i386 build from ever running. That was corrected this morning so it
should run tonight.
2. The Window
