Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the YAML CPAN distribution.

Report information
The Basics
Id: 92544
Status: resolved
Priority: 0/
Queue: YAML
People
Owner: Nobody in particular
Requestors: jmarshall [...] acquiremedia.com
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: 1.24_001

History Show all quoted text
  Tue Jan 28 15:05:41 2014 jmarshall [...] acquiremedia.com - Ticket created
Subject: crash on long string [YAML #90593]
Date: Tue, 28 Jan 2014 15:04:20 -0500
To: bug-YAML [...] rt.cpan.org, Thorsten Eckel <thorsten.eckel [...] otrs.com>, Ingy döt Net <ingy [...] ingy.net>
From: "Jonathan A. Marshall" <jmarshall [...] acquiremedia.com>
RT#90593 claims that this bug was fixed in version 0.85. But I am still encountering this problem in YAML version 0.88, using Perl 5.8.8. Simple test: just run t/rt-90593.t. It crashes at line 518, during the invocation of $self->inline. This indicates a problem with the inline() function. The crash does not occur at that location when I replace $self->inline with $self->{inline}. Thanks and best wishes, --Jonathan
  Wed Jan 29 14:11:49 2014 jmarshall [...] acquiremedia.com - Correspondence added
Subject: Re: [rt.cpan.org #92544] AutoReply: crash on long string [YAML #90593]
Date: Wed, 29 Jan 2014 12:23:36 -0500
To: "bug-YAML [...] rt.cpan.org" <bug-YAML [...] rt.cpan.org>
From: "Jonathan A. Marshall" <jmarshall [...] acquiremedia.com>
For example: # perl /root/.cpan/build/YAML-0.88-3Nx_t3/t/rt-90593.t 1..2 Segmentation fault # Thanks, --Jonathan On 01/28/2014 03:05 PM, Bugs in YAML via RT wrote: Show quoted text
> Greetings, > This message has been automatically generated in response to the > creation of a trouble ticket regarding: > "crash on long string [YAML #90593]", > a summary of which appears below. > > There is no need to reply to this message right now. Your ticket has been > assigned an ID of [rt.cpan.org #92544]. Your ticket is accessible > on the web at: https://rt.cpan.org/Ticket/Display.html?id=92544 > > Please include the string: [rt.cpan.org #92544] > in the subject line of all future correspondence about this issue. To do so, > you may reply to this message. > Thank you, > bug-YAML@rt.cpan.org > ------------------------------------------------------------------------- > RT#90593 claims that this bug was fixed in version 0.85. But I am still > encountering this problem in YAML version 0.88, using Perl 5.8.8. > > Simple test: just run t/rt-90593.t. It crashes at line 518, during the > invocation of $self->inline. This indicates a problem with the inline() > function. The crash does not occur at that location when I replace > $self->inline with $self->{inline}. > > Thanks and best wishes, > --Jonathan
  Thu Aug 14 02:53:09 2014 ingy [...] cpan.org - Correspondence added
This issue has been copied to: https://github.com/ingydotnet/yaml-pm/issues/134 please take all future correspondence there. This ticket will remain open but please do not reply here. This ticket will be closed when the github issue is dealt with.
  Thu Aug 14 02:53:10 2014 The RT System itself - Status changed from 'new' to 'open'
  Wed May 09 19:13:56 2018 TINITA [...] cpan.org - Correspondence added
should be fixed in 1.24_001
  Wed May 09 19:13:57 2018 TINITA [...] cpan.org - Status changed from 'open' to 'resolved'
  Wed May 09 19:13:57 2018 TINITA [...] cpan.org - Fixed in 1.24_001 added
  Wed May 09 19:35:41 2018 jonathan.marshall [...] newscycle.com - Correspondence added
Subject: Re: [rt.cpan.org #92544] Resolved: crash on long string [YAML #90593]
Date: Wed, 09 May 2018 19:34:28 -0400
To: bug-YAML [...] rt.cpan.org,Tina Muller via RT <bug-YAML [...] rt.cpan.org>,jmarshall [...] acquiremedia.com
From: "Jonathan A. Marshall" <jonathan.marshall [...] newscycle.com>
Thank you, Tinita. --Jonathan On May 9, 2018 7:13:57 PM EDT, Tina Muller via RT <bug-YAML@rt.cpan.org> wrote: Show quoted text
><URL: https://rt.cpan.org/Ticket/Display.html?id=92544 > > >According to our records, your request has been resolved. If you have >any >further questions or concerns, please respond to this message.