Calling tuple struct constructor as a function causes segfault

This code segfaults (as of a5fae1d 2013-03-08 18:15:40 -0800).

struct A(int);
fn main() {
    let f: extern pure fn(int) -> A = A; f(4);
}

Note that extern pure fn(int) -> A is an exact type reported by the compiler for A. This occurs for arbitrary number of fields. Replacing the body of main to A(4); fixes the segfault.

Reproduced with 517bfc9 .

The bug also comes up if you omit the type signature on f. I poked at this a little bit -- it looks like trans stores a **fn(int) into f, but the code generated for the call f(4) treats `fas if it's a*f``. Then I got confused as to which part of the code was correct. I think this isn't critical for 0.7.

Nominating for milestone 5 (production-ready).

accepted for production-ready milestone

tuple struct constructor as function is going away with a patch I'm working on.

So that patch never really worked out. But, this is still relevant, and reproduces.

auto merge of #8580 : bytewiseand/rust/tuple-struct-ctor-ptr, r=alexc…

Merge rust-lang#5315

Merge pull request rust-lang#5315 from RalfJung/sig-ptr-types

Navigation Menu

Repository navigation

Calling tuple struct constructor as a function causes segfault #5315

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Calling tuple struct constructor as a function causes segfault #5315

Description

Activity

catamorphism commented on May 9, 2013

catamorphism commented on May 9, 2013

graydon commented on May 16, 2013

emberian commented on Jun 22, 2013

emberian commented on Aug 5, 2013

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions