This is the mail archive of the
kawa@sourceware.org
mailing list for the Kawa project.
Re: StackOverflow
- From: Matthieu Vachon <matthieu dot o dot vachon at gmail dot com>
- To: Per Bothner <per at bothner dot com>
- Cc: "kawa at sourceware dot org" <kawa at sourceware dot org>
- Date: Wed, 27 Nov 2013 11:15:45 -0500
- Subject: Re: StackOverflow
- Authentication-results: sourceware.org; auth=none
- References: <CAOTvmo=JcUiYA8=1jZR4E5qDpzLLugaUH8TtyAZqxJkfZaZujA at mail dot gmail dot com> <52853183 dot 2010108 at bothner dot com> <CAOTvmomhucyWYiKYmQ_qfvfPAmxfFSM0mQ8S-Rr9v+f_XRMvyA at mail dot gmail dot com>
Just to let you know that I got the error again this morning. It was
after about 3 hours of intense usage. I forgot to copy the stack but
it was around the same place as the last time.
I will add the debugging code you gave my since it's highly possible
that I will hit again. Will report you with the information if it
happen again.
On Thu, Nov 14, 2013 at 4:33 PM, Matthieu Vachon
<matthieu.o.vachon@gmail.com> wrote:
> On Thu, Nov 14, 2013 at 3:24 PM, Per Bothner <per@bothner.com> wrote:
>>
>> That may take it hard to debug. But some ideas:
>
> Indeed, that will not be easy. I used the application for two hours
> now and the problem did not re-appear. I don't have much hope to
> reproduce it easily. Nobody here ever reported this problem to me yet.
>
>>
>> If this triggers that can provide some clues. Of course if it's repeatable
>> and
>> you have Locations with the same Location.id show up then it is (relatively)
>> easy to debug.
>>
>
> Will look into it next time I update our Kawa version. Our current
> build structure does not make it easy to update Kawa to its latest
> version :)
>
>>
>> My guess the problem will trigger in CYCLE1. Maybe the name will allow you
>> do to
>> map back to the corresponding source definition - perhaps an implicit or
>> explicit define-variable. This code is pretty old, so I'd have to do some
>> reviewing as to what is supposed to happen.
>
> Thanks for looking into, but there is no rush. This is clearly not a
> big problem for us right now.
>
> Matt