[Pharo-project] What happens with Warning when running in headless image (2.0)?

Gastón Dall' Oglio gaston.dalloglio at gmail.com
Fri Aug 31 15:31:11 CEST 2012


Somebody send recently similar mail to pharo-user list "[Pharo-users] HowTo
not show a Debugger when calling deprecated methods in 1.4?"


2012/8/31 Gastón Dall' Oglio <gaston.dalloglio at gmail.com>

> Hi Igor.
>
> Here, in a linux box, I guess that this warning occurs and raise the
> NonInteractiveUIManager exception, and is showed in stdout when I run in
> headless mode.
>
>
> 2012/8/31 Igor Stasenko <siguctua at gmail.com>
>
>> in headless mode all warnings are suppressed (so they don't interfere).
>> i'm not sure if it prints something on stdout..
>> it could be that it simply ignored and continues running the stuff.
>>
>> On 31 August 2012 14:11, Gastón Dall' Oglio <gaston.dalloglio at gmail.com>
>> wrote:
>> > Hello.
>> >
>> > I install Seaside in a Pharo 1.4 summer image. Then I run it in headless
>> > from console and I go to the /status app, and a "MessageNotUnderstood:
>> >
>> NonInteractiveUIManager>>openDebuggerOn:context:label:contents:fullView:"
>> > exception occurs and the vm close.
>> >
>> > Then I run this image in gui and an "Deprecation: The method
>> > SmalltalkImage>>isRunningCog has been deprecated." dialog box are
>> raised. I
>> > evaluate Deprecation raiseWarning: false but no take effect, the dialog
>> is
>> > raised anyway.
>> >
>> > Maybe another is correct way to disable raise deprecation?
>> >
>> > 2012/8/31 Camillo Bruni <camillobruni at gmail.com>
>> >>
>> >> if run from the command line you should get a decent error message...
>> >>
>> >> what kind of error do you get?
>> >>
>> >> BTW: just show me the code and I'll fix it :P
>> >>
>> >> On 2012-08-31, at 07:24, Dale Henrichs <dhenrich at vmware.com> wrote:
>> >>
>> >> > I'm running a headless pharo2.0 from a script and the vm disappears
>> >> > without a trace (no pharodebug.log info etc.) ... when I run the
>> script in a
>> >> > gui, I see that a warning dialog box is popping up, so perhaps this
>> is the
>> >> > source of the issue? ... or perhaps it's something else?
>> >> >
>> >> > Dale
>> >> >
>> >>
>> >>
>> >
>>
>>
>>
>> --
>> Best regards,
>> Igor Stasenko.
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gforge.inria.fr/pipermail/pharo-project/attachments/20120831/65547fef/attachment.html>


More information about the Pharo-project mailing list