Ticket #643 (closed bug: fixed)

Opened 5 years ago

Last modified 5 years ago

Segfault while compiling fperrad's lua

Reported by: losinggeneration Owned by: whiteknight
Priority: major Milestone:
Component: core Version: 1.1.0
Severity: medium Keywords: crash segfault lua
Cc: Language:
Patch status: Platform: linux

Description

Compiling Lua on Parrot ( http://github.com/fperrad/lua/tree/master) crashes parrot

Attachments

fperrad.crash.report Download (5.0 KB) - added by losinggeneration 5 years ago.
crash report from parrotbug

Change History

Changed 5 years ago by losinggeneration

crash report from parrotbug

follow-up: ↓ 2   Changed 5 years ago by jkeenan

Is this the same problem as was reported in TT #541?

in reply to: ↑ 1   Changed 5 years ago by losinggeneration

Replying to jkeenan:

Is this the same problem as was reported in TT #541?

It looks pretty close, if it's not quit the same, it's because I was using a fairly recent (yesterday) pull from svn. So at the very least it confirms it's still a problem in svn.

follow-up: ↓ 5   Changed 5 years ago by whiteknight

  • owner set to whiteknight

This issue is 7 months old now. Questions:

  • Does Lua currently build?
  • Does it not build on any particular platforms?
  • Can we get any confirmation that there is still a crash during the lua build with Parrot 1.8.0 or later?

  Changed 5 years ago by fperrad

Currently (ie Parrot-1.8.0), Lua build without problem on win32 & on linux-i386.

in reply to: ↑ 3   Changed 5 years ago by losinggeneration

Replying to whiteknight:

This issue is 7 months old now. Questions: - Does Lua currently build? - Does it not build on any particular platforms? - Can we get any confirmation that there is still a crash during the lua build with Parrot 1.8.0 or later?

I'm pretty sure this can be marked as closed. I should have remembered to say something when things started building again, but it totally slipped my mind. Anyways, it's a non-issue (unless the crash report is still of any use) at this point.

  Changed 5 years ago by jkeenan

  • status changed from new to closed
  • resolution set to fixed

On the basis of the comments by François and the original poster, I think we can close this ticket.

kid51

Note: See TracTickets for help on using tickets.