Is the backtrace broken in 2.2.2?

Is the backtrace broken in 2.2.2?

[Nala Ginrut]

Hi all!
I'm using the latest Guile from git repo.
It seems something is wrong to print message of backtrace.

-----------------------cut------------------------
Exception thrown while printing backtrace:
ERROR: In procedure vector-ref: Value out of range: 156
------------------------end----------------------

Any thoughts?

Best regards.

Re: Is the backtrace broken in 2.2.2?

[Andy Wingo]

On Mon 01 May 2017 06:45, Nala Ginrut <nalaginrut@gmail.com> writes:

> Hi all!
> I'm using the latest Guile from git repo.
> It seems something is wrong to print message of backtrace.
>
> -----------------------cut------------------------
> Exception thrown while printing backtrace:
> ERROR: In procedure vector-ref: Value out of range: 156
> ------------------------end----------------------
>
> Any thoughts?

Always or just sometimes?  Needs a test case :)

Note that there was this, in the past:
4dcc97288dc2c43ea9f2e61fdb1357cec3936fc9.  But that was fixed.

Andy

Re: Is the backtrace broken in 2.2.2?

[Nala Ginrut]

It always appears. Maybe relate to call-with-prompt?

On Wed, May 3, 2017 at 3:45 AM, Andy Wingo <wingo@pobox.com> wrote:
> On Mon 01 May 2017 06:45, Nala Ginrut <nalaginrut@gmail.com> writes:
>
>> Hi all!
>> I'm using the latest Guile from git repo.
>> It seems something is wrong to print message of backtrace.
>>
>> -----------------------cut------------------------
>> Exception thrown while printing backtrace:
>> ERROR: In procedure vector-ref: Value out of range: 156
>> ------------------------end----------------------
>>
>> Any thoughts?
>
> Always or just sometimes?  Needs a test case :)
>
> Note that there was this, in the past:
> 4dcc97288dc2c43ea9f2e61fdb1357cec3936fc9.  But that was fixed.
>
> Andy

Re: Is the backtrace broken in 2.2.2?

[Mark H Weaver]

Nala Ginrut <nalaginrut@gmail.com> writes:

> On Wed, May 3, 2017 at 3:45 AM, Andy Wingo <wingo@pobox.com> wrote:
>> On Mon 01 May 2017 06:45, Nala Ginrut <nalaginrut@gmail.com> writes:
>>
>>> Hi all!
>>> I'm using the latest Guile from git repo.
>>> It seems something is wrong to print message of backtrace.
>>>
>>> -----------------------cut------------------------
>>> Exception thrown while printing backtrace:
>>> ERROR: In procedure vector-ref: Value out of range: 156
>>> ------------------------end----------------------
>>>
>>> Any thoughts?
>>
>> Always or just sometimes?  Needs a test case :)
>>
>> Note that there was this, in the past:
>> 4dcc97288dc2c43ea9f2e61fdb1357cec3936fc9.  But that was fixed.

> It always appears. Maybe relate to call-with-prompt?

Can you provide a small self-contained test case to demonstrate the
problem, so that we can reproduce it on our systems?

      Mark

Re: Is the backtrace broken in 2.2.2?

[Nala Ginrut]

[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]

I'm trying to form a simplified test case, please wait a moment.


2017年5月13日 06:21，"Mark H Weaver" <mhw@netris.org>写道：

> Nala Ginrut <nalaginrut@gmail.com> writes:
>
> > On Wed, May 3, 2017 at 3:45 AM, Andy Wingo <wingo@pobox.com> wrote:
> >> On Mon 01 May 2017 06:45, Nala Ginrut <nalaginrut@gmail.com> writes:
> >>
> >>> Hi all!
> >>> I'm using the latest Guile from git repo.
> >>> It seems something is wrong to print message of backtrace.
> >>>
> >>> -----------------------cut------------------------
> >>> Exception thrown while printing backtrace:
> >>> ERROR: In procedure vector-ref: Value out of range: 156
> >>> ------------------------end----------------------
> >>>
> >>> Any thoughts?
> >>
> >> Always or just sometimes?  Needs a test case :)
> >>
> >> Note that there was this, in the past:
> >> 4dcc97288dc2c43ea9f2e61fdb1357cec3936fc9.  But that was fixed.
>
> > It always appears. Maybe relate to call-with-prompt?
>
> Can you provide a small self-contained test case to demonstrate the
> problem, so that we can reproduce it on our systems?
>
>       Mark
>

[-- Attachment #2: Type: text/html, Size: 1783 bytes --]