Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Calling get() method of std.deque causes a segfault. #138

Closed
froystig opened this issue Jul 28, 2010 · 3 comments
Closed

Calling get() method of std.deque causes a segfault. #138

froystig opened this issue Jul 28, 2010 · 3 comments

Comments

@froystig
Copy link
Contributor

Other methods of the deque that perform a similar operation do not cause trouble, but this one does.

@tohava
Copy link
Contributor

tohava commented Aug 8, 2010

This problem remains if one modifies the get() function to ignore it's int parameter and always use 0. However, this problem goes away if one then deletes the int parameter. The segmentatino fault itself occurs when entering the function, at what appears to be some prelude code added by the rust compiler which occur before the function begins. I also suspect modifying the function to return nothing might affect the SEGV somehow.

@tohava
Copy link
Contributor

tohava commented Aug 8, 2010

To be more specific, the problem occurs in code emitted by the call to calculate_sz within fn_prologoue. That call recurses through itself until it reaches the SIZE_param_size case, in which it emits an instruction that when executed causes a segmentation fault for get().

If anyone can explain that code to me I can probably get closer to solving this.

@froystig
Copy link
Contributor Author

Get object's captured typarams when querying for an object method's typarams in Trans. Together with commit 982dcc2 this... Closed by fd0750b.

mbrubeck pushed a commit to mbrubeck/rust that referenced this issue Oct 17, 2011
oli-obk pushed a commit to oli-obk/rust that referenced this issue Jul 19, 2017
refactor lvalue field projection handling to prepare for fewer `force_allocation`s
keeperofdakeys pushed a commit to keeperofdakeys/rust that referenced this issue Dec 12, 2017
dlrobertson pushed a commit to dlrobertson/rust that referenced this issue Nov 29, 2018
rchaser53 pushed a commit to rchaser53/rust that referenced this issue Jan 19, 2019
bors pushed a commit to rust-lang-ci/rust that referenced this issue Oct 1, 2021
Add various fns
- Sum/Product traits
- recip/to_degrees/to_radians/min/max/clamp/signum/copysign; rust-lang/portable-simd#14
- mul_add: rust-lang/portable-simd#14, fixes rust-lang/portable-simd#102
ZuseZ4 referenced this issue in EnzymeAD/rust Mar 7, 2023
* Fix release tags


Co-authored-by: Valentin Churavy <vchuravy@users.noreply.github.com>
celinval pushed a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants