Hello,
Rick McGuire wrote:
> I've not found a debugger for Linux that I consider usable. I loathe
> gdb with a passion. I've had occasional luck with the gdb front end
> in Slickedit, but it has a number of issues that make it difficult to
> use. If I'm lucky, the bug I'm looking at is cross pl
Are you loading this by registering the instance in memory, or by
explicitly requesting a library to be loaded? And if you'd like a
fix, the appropriate means for requesting that is to open a bug
report.
Rck
On Wed, Jun 3, 2009 at 2:45 AM, Rony G. Flatscher
wrote:
> Just for the record: current
Rick McGuire wrote:
> Are you loading this by registering the instance in memory, or by
> explicitly requesting a library to be loaded?
The library gets loaded via Java once.
Then, whenever a Rexx instance is created in native code via JNI, the
optionName "REGISTER_LIBRARY" is used to register t
I don't find any code path that would cause that to happen, so I'll
need a test case that recreates the problem.
Rick
On Wed, Jun 3, 2009 at 6:28 AM, Rony G. Flatscher
wrote:
> Rick McGuire wrote:
>> Are you loading this by registering the instance in memory, or by
>> explicitly requesting a lib
Rick McGuire wrote:
> I don't find any code path that would cause that to happen, so I'll
> need a test case that recreates the problem.
>
O.K., but it will take some time.
---rony
--
OpenSolaris 2009.06 is a cutting
If sounds like you already have something that reproduces this. You
can email this directly to me once you've opened a bug if it is too
large to attach.
Rick
On Wed, Jun 3, 2009 at 6:36 AM, Rony G. Flatscher
wrote:
>
> Rick McGuire wrote:
>> I don't find any code path that would cause that to h
Rick McGuire wrote:
> If sounds like you already have something that reproduces this. You
> can email this directly to me once you've opened a bug if it is too
> large to attach.
>
O.K, thanks.
One problem being, that I need to pack up all pieces of Java classes and
test them stand-alone in or
All I need is something to run so I can debug what Rexx is doing. All
the rest of the stuff is just noise. There either is a bug there, in
which case it will be obvious from the debugger, or this is an error
in your assumptions, which will also be quickly obvious.
Rick
On Wed, Jun 3, 2009 at 8:
Hello,
if I did not miss something there is no explicit signal handler for
SIGTERM in the API daemon.
Sometimes a simple kill does not terminate the daemon.
Would it be a problem if I add a signal handler for SIGTERM ?
My idea is to add an handler which calls apiServer.terminateServer(); ...
Is
