[#4479] Requesting addition to IRB (configurable standard output) — Sascha Ebach <se@...>

Hello,

13 messages 2005/02/24
[#4482] Re: Requesting addition to IRB (configurable standard output) — Sam Roberts <sroberts@...> 2005/02/25

Quoting se@digitale-wertschoepfung.de, on Fri, Feb 25, 2005 at 01:22:34AM +0900:

[#4483] Re: Requesting addition to IRB (configurable standard output) — Eric Hodel <drbrain@...7.net> 2005/02/25

On 24 Feb 2005, at 19:51, Sam Roberts wrote:

[#4488] Re: Requesting addition to IRB (configurable standard output) — Sam Roberts <sroberts@...> 2005/02/26

Quoting drbrain@segment7.net, on Sat, Feb 26, 2005 at 02:43:31AM +0900:

[#4489] Re: Requesting addition to IRB (configurable standard output) — Eric Hodel <drbrain@...7.net> 2005/02/26

On 25 Feb 2005, at 16:03, Sam Roberts wrote:

Re: SecurityError on Method#call? (might be DRb specific)

From: Pit Capitain <pit@...>
Date: 2005-02-15 07:34:17 UTC
List: ruby-core #4433
Florian Groschrieb:
> I've recently having trouble with these kind of errors:
> 
>> SecurityError in  Member#list
>>  
>> Insecure operation `write' at level 4
 >
 > ...
> 
> I can not reproduce the problem locally, but some users of the 
> breakpoint library where this trouble can reproduce it reliably, so I'll 
> be able to pass along further questions.

I've no idea either, but what are the differences between your environment and 
those where the problem can be reproduced? Do your users have the possiblity to 
set a breakpoint (in C, not Ruby ;-) at the point where the SecurityError is 
raised? (In Ruby 1.8.2 there seems to be exactly one place.) How does the Ruby 
exception backtrace look like?

Just some thoughts.

Regards,
Pit

In This Thread

Prev Next