You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@buildr.apache.org by hemant <ge...@gmail.com> on 2009/05/12 15:23:43 UTC
Scala Compiler Crash errors
buildr swallows the error silently with "unknown exception" if the compiler
crashes for some reason. I think whatever stacktrace with which the compiler
crashed should be printed to STDOUT.
Re: Scala Compiler Crash errors
Posted by Daniel Spiewak <dj...@gmail.com>.
Ah, that explains it. I've seen RJB eat scalac's exceptions on occasion,
even when being invoked directly.
Daniel
On Thu, May 14, 2009 at 3:57 AM, hemant <ge...@gmail.com> wrote:
> MRI
>
>
>
> On Thu, May 14, 2009 at 6:23 AM, Daniel Spiewak <dj...@gmail.com>
> wrote:
>
> > fsc -reset Solves a whole myriad of problems. :-)
> >
> > One quick question: are you using JRuby or MRI?
> >
> > Daniel
> >
> >
> > On May 13, 2009, at 7:44 PM, hemant <ge...@gmail.com> wrote:
> >
> > Hey Daniel,
> >>
> >> I am aware of all that and like many sane Scala developers I try to stay
> >> away for FSC. However my bug report has nothing todo with FSC i think.
> >>
> >>
> >>
> >> On Thu, May 14, 2009 at 4:40 AM, Daniel Spiewak <dj...@gmail.com>
> >> wrote:
> >>
> >> Buildr will automatically use fsc if USE_FSC is set to "yes". If not,
> >>> then
> >>> it invokes the conventional Scala compiler in the current JVM instance
> >>> (it
> >>> doesn't incur any extra startup overhead).
> >>>
> >>> Daniel
> >>>
> >>> On Wed, May 13, 2009 at 1:23 PM, hemant <ge...@gmail.com> wrote:
> >>>
> >>> Odd, I am not using fsc at all or are you driving at you should set
> >>>> USE_FSC="no" even when you are not using "fsc" ??
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> On Tue, May 12, 2009 at 7:45 PM, Daniel Spiewak <dj...@gmail.com>
> >>>> wrote:
> >>>>
> >>>> I've noticed that. Actually, if you set USE_FSC to "no", you should
> >>>>>
> >>>> see
> >>>
> >>>> the exception. As for compilation with fsc, this issue is on my list
> >>>>>
> >>>> of
> >>>
> >>>> stuff to look at.
> >>>>>
> >>>>> Daniel
> >>>>>
> >>>>>
> >>>>> On May 12, 2009, at 8:23 AM, hemant <ge...@gmail.com> wrote:
> >>>>>
> >>>>> buildr swallows the error silently with "unknown exception" if the
> >>>>>
> >>>>>> compiler
> >>>>>> crashes for some reason. I think whatever stacktrace with which the
> >>>>>> compiler
> >>>>>> crashed should be printed to STDOUT.
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>> --
> >>>> Let them talk of their oriental summer climes of everlasting
> >>>> conservatories;
> >>>> give me the privilege of making my own summer with my own coals.
> >>>>
> >>>> http://gnufied.org
> >>>>
> >>>>
> >>>
> >>
> >>
> >> --
> >> Let them talk of their oriental summer climes of everlasting
> >> conservatories;
> >> give me the privilege of making my own summer with my own coals.
> >>
> >> http://gnufied.org
> >>
> >
>
>
> --
> Let them talk of their oriental summer climes of everlasting
> conservatories;
> give me the privilege of making my own summer with my own coals.
>
> http://gnufied.org
>
Re: Scala Compiler Crash errors
Posted by hemant <ge...@gmail.com>.
MRI
On Thu, May 14, 2009 at 6:23 AM, Daniel Spiewak <dj...@gmail.com> wrote:
> fsc -reset Solves a whole myriad of problems. :-)
>
> One quick question: are you using JRuby or MRI?
>
> Daniel
>
>
> On May 13, 2009, at 7:44 PM, hemant <ge...@gmail.com> wrote:
>
> Hey Daniel,
>>
>> I am aware of all that and like many sane Scala developers I try to stay
>> away for FSC. However my bug report has nothing todo with FSC i think.
>>
>>
>>
>> On Thu, May 14, 2009 at 4:40 AM, Daniel Spiewak <dj...@gmail.com>
>> wrote:
>>
>> Buildr will automatically use fsc if USE_FSC is set to "yes". If not,
>>> then
>>> it invokes the conventional Scala compiler in the current JVM instance
>>> (it
>>> doesn't incur any extra startup overhead).
>>>
>>> Daniel
>>>
>>> On Wed, May 13, 2009 at 1:23 PM, hemant <ge...@gmail.com> wrote:
>>>
>>> Odd, I am not using fsc at all or are you driving at you should set
>>>> USE_FSC="no" even when you are not using "fsc" ??
>>>>
>>>>
>>>>
>>>>
>>>> On Tue, May 12, 2009 at 7:45 PM, Daniel Spiewak <dj...@gmail.com>
>>>> wrote:
>>>>
>>>> I've noticed that. Actually, if you set USE_FSC to "no", you should
>>>>>
>>>> see
>>>
>>>> the exception. As for compilation with fsc, this issue is on my list
>>>>>
>>>> of
>>>
>>>> stuff to look at.
>>>>>
>>>>> Daniel
>>>>>
>>>>>
>>>>> On May 12, 2009, at 8:23 AM, hemant <ge...@gmail.com> wrote:
>>>>>
>>>>> buildr swallows the error silently with "unknown exception" if the
>>>>>
>>>>>> compiler
>>>>>> crashes for some reason. I think whatever stacktrace with which the
>>>>>> compiler
>>>>>> crashed should be printed to STDOUT.
>>>>>>
>>>>>>
>>>>>
>>>>
>>>> --
>>>> Let them talk of their oriental summer climes of everlasting
>>>> conservatories;
>>>> give me the privilege of making my own summer with my own coals.
>>>>
>>>> http://gnufied.org
>>>>
>>>>
>>>
>>
>>
>> --
>> Let them talk of their oriental summer climes of everlasting
>> conservatories;
>> give me the privilege of making my own summer with my own coals.
>>
>> http://gnufied.org
>>
>
--
Let them talk of their oriental summer climes of everlasting conservatories;
give me the privilege of making my own summer with my own coals.
http://gnufied.org
Re: Scala Compiler Crash errors
Posted by Daniel Spiewak <dj...@gmail.com>.
fsc -reset Solves a whole myriad of problems. :-)
One quick question: are you using JRuby or MRI?
Daniel
On May 13, 2009, at 7:44 PM, hemant <ge...@gmail.com> wrote:
> Hey Daniel,
>
> I am aware of all that and like many sane Scala developers I try to
> stay
> away for FSC. However my bug report has nothing todo with FSC i think.
>
>
>
> On Thu, May 14, 2009 at 4:40 AM, Daniel Spiewak
> <dj...@gmail.com> wrote:
>
>> Buildr will automatically use fsc if USE_FSC is set to "yes". If
>> not, then
>> it invokes the conventional Scala compiler in the current JVM
>> instance (it
>> doesn't incur any extra startup overhead).
>>
>> Daniel
>>
>> On Wed, May 13, 2009 at 1:23 PM, hemant <ge...@gmail.com> wrote:
>>
>>> Odd, I am not using fsc at all or are you driving at you should set
>>> USE_FSC="no" even when you are not using "fsc" ??
>>>
>>>
>>>
>>>
>>> On Tue, May 12, 2009 at 7:45 PM, Daniel Spiewak
>>> <dj...@gmail.com>
>>> wrote:
>>>
>>>> I've noticed that. Actually, if you set USE_FSC to "no", you
>>>> should
>> see
>>>> the exception. As for compilation with fsc, this issue is on my
>>>> list
>> of
>>>> stuff to look at.
>>>>
>>>> Daniel
>>>>
>>>>
>>>> On May 12, 2009, at 8:23 AM, hemant <ge...@gmail.com> wrote:
>>>>
>>>> buildr swallows the error silently with "unknown exception" if the
>>>>> compiler
>>>>> crashes for some reason. I think whatever stacktrace with which
>>>>> the
>>>>> compiler
>>>>> crashed should be printed to STDOUT.
>>>>>
>>>>
>>>
>>>
>>> --
>>> Let them talk of their oriental summer climes of everlasting
>>> conservatories;
>>> give me the privilege of making my own summer with my own coals.
>>>
>>> http://gnufied.org
>>>
>>
>
>
>
> --
> Let them talk of their oriental summer climes of everlasting
> conservatories;
> give me the privilege of making my own summer with my own coals.
>
> http://gnufied.org
Re: Scala Compiler Crash errors
Posted by hemant <ge...@gmail.com>.
Hey Daniel,
I am aware of all that and like many sane Scala developers I try to stay
away for FSC. However my bug report has nothing todo with FSC i think.
On Thu, May 14, 2009 at 4:40 AM, Daniel Spiewak <dj...@gmail.com> wrote:
> Buildr will automatically use fsc if USE_FSC is set to "yes". If not, then
> it invokes the conventional Scala compiler in the current JVM instance (it
> doesn't incur any extra startup overhead).
>
> Daniel
>
> On Wed, May 13, 2009 at 1:23 PM, hemant <ge...@gmail.com> wrote:
>
> > Odd, I am not using fsc at all or are you driving at you should set
> > USE_FSC="no" even when you are not using "fsc" ??
> >
> >
> >
> >
> > On Tue, May 12, 2009 at 7:45 PM, Daniel Spiewak <dj...@gmail.com>
> > wrote:
> >
> > > I've noticed that. Actually, if you set USE_FSC to "no", you should
> see
> > > the exception. As for compilation with fsc, this issue is on my list
> of
> > > stuff to look at.
> > >
> > > Daniel
> > >
> > >
> > > On May 12, 2009, at 8:23 AM, hemant <ge...@gmail.com> wrote:
> > >
> > > buildr swallows the error silently with "unknown exception" if the
> > >> compiler
> > >> crashes for some reason. I think whatever stacktrace with which the
> > >> compiler
> > >> crashed should be printed to STDOUT.
> > >>
> > >
> >
> >
> > --
> > Let them talk of their oriental summer climes of everlasting
> > conservatories;
> > give me the privilege of making my own summer with my own coals.
> >
> > http://gnufied.org
> >
>
--
Let them talk of their oriental summer climes of everlasting conservatories;
give me the privilege of making my own summer with my own coals.
http://gnufied.org
Re: Scala Compiler Crash errors
Posted by Daniel Spiewak <dj...@gmail.com>.
Buildr will automatically use fsc if USE_FSC is set to "yes". If not, then
it invokes the conventional Scala compiler in the current JVM instance (it
doesn't incur any extra startup overhead).
Daniel
On Wed, May 13, 2009 at 1:23 PM, hemant <ge...@gmail.com> wrote:
> Odd, I am not using fsc at all or are you driving at you should set
> USE_FSC="no" even when you are not using "fsc" ??
>
>
>
>
> On Tue, May 12, 2009 at 7:45 PM, Daniel Spiewak <dj...@gmail.com>
> wrote:
>
> > I've noticed that. Actually, if you set USE_FSC to "no", you should see
> > the exception. As for compilation with fsc, this issue is on my list of
> > stuff to look at.
> >
> > Daniel
> >
> >
> > On May 12, 2009, at 8:23 AM, hemant <ge...@gmail.com> wrote:
> >
> > buildr swallows the error silently with "unknown exception" if the
> >> compiler
> >> crashes for some reason. I think whatever stacktrace with which the
> >> compiler
> >> crashed should be printed to STDOUT.
> >>
> >
>
>
> --
> Let them talk of their oriental summer climes of everlasting
> conservatories;
> give me the privilege of making my own summer with my own coals.
>
> http://gnufied.org
>
Re: Scala Compiler Crash errors
Posted by hemant <ge...@gmail.com>.
Odd, I am not using fsc at all or are you driving at you should set
USE_FSC="no" even when you are not using "fsc" ??
On Tue, May 12, 2009 at 7:45 PM, Daniel Spiewak <dj...@gmail.com> wrote:
> I've noticed that. Actually, if you set USE_FSC to "no", you should see
> the exception. As for compilation with fsc, this issue is on my list of
> stuff to look at.
>
> Daniel
>
>
> On May 12, 2009, at 8:23 AM, hemant <ge...@gmail.com> wrote:
>
> buildr swallows the error silently with "unknown exception" if the
>> compiler
>> crashes for some reason. I think whatever stacktrace with which the
>> compiler
>> crashed should be printed to STDOUT.
>>
>
--
Let them talk of their oriental summer climes of everlasting conservatories;
give me the privilege of making my own summer with my own coals.
http://gnufied.org
Re: Scala Compiler Crash errors
Posted by Daniel Spiewak <dj...@gmail.com>.
I've noticed that. Actually, if you set USE_FSC to "no", you should
see the exception. As for compilation with fsc, this issue is on my
list of stuff to look at.
Daniel
On May 12, 2009, at 8:23 AM, hemant <ge...@gmail.com> wrote:
> buildr swallows the error silently with "unknown exception" if the
> compiler
> crashes for some reason. I think whatever stacktrace with which the
> compiler
> crashed should be printed to STDOUT.
Re: Scala Compiler Crash errors
Posted by hemant <ge...@gmail.com>.
Hi Alex,
Okay I have created the bug report and attached a sample scala program that
crashes the compiler (with 2.7.3 or 2.7.4).
https://issues.apache.org/jira/browse/BUILDR-279
On Thu, May 14, 2009 at 5:56 AM, Alex Boisvert <bo...@intalio.com> wrote:
> On Tue, May 12, 2009 at 6:23 AM, hemant <ge...@gmail.com> wrote:
>
> > buildr swallows the error silently with "unknown exception" if the
> compiler
> > crashes for some reason. I think whatever stacktrace with which the
> > compiler
> > crashed should be printed to STDOUT.
> >
>
> It would be cool if you could open a bug and attach a simple .scala file
> that crashes the compiler. I've seen plenty of those but I don't have one
> handy at the moment.
>
> alex
>
--
Let them talk of their oriental summer climes of everlasting conservatories;
give me the privilege of making my own summer with my own coals.
http://gnufied.org
Re: Scala Compiler Crash errors
Posted by Alex Boisvert <bo...@intalio.com>.
On Tue, May 12, 2009 at 6:23 AM, hemant <ge...@gmail.com> wrote:
> buildr swallows the error silently with "unknown exception" if the compiler
> crashes for some reason. I think whatever stacktrace with which the
> compiler
> crashed should be printed to STDOUT.
>
It would be cool if you could open a bug and attach a simple .scala file
that crashes the compiler. I've seen plenty of those but I don't have one
handy at the moment.
alex