Skip to content

warnings and pretty-printer output sometimes seem to mix on FreeBSD #2520

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.

Sign up for GitHub

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

Jump to bottom
Closed
catamorphism opened this issue Jun 7, 2012 · 2 comments
Closed

warnings and pretty-printer output sometimes seem to mix on FreeBSD #2520

catamorphism opened this issue Jun 7, 2012 · 2 comments
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc
Milestone
0.4

Comments

@catamorphism
Copy link
Contributor

This causes tests to fail pretty-printing on the FreeBSD buildbot, seemingly at random. Possibly a problem with how to redirect stderr and stdout.
@crabtw crabtw mentioned this issue Jun 7, 2012
Merged
@catamorphism
Copy link
Contributor Author

Should be fixed by #2523, which I've merged, but waiting for the tests to finish running.

@ghost ghost assigned catamorphism Jun 7, 2012
@crabtw crabtw mentioned this issue Jun 7, 2012
Closed
@catamorphism
Copy link
Contributor Author

FreeBSD tests pass, so I'm considering this done, thanks to @crabtw .

@catamorphism catamorphism removed their assignment Jun 16, 2014
RalfJung pushed a commit to RalfJung/rust that referenced this issue Jun 29, 2023
@bors
Auto merge of rust-lang#2520 - saethlin:mmap-shim, r=RalfJung
b621c4d 
mmap/munmap/mremamp shims

This adds basic support for `mmap`/`mremap`/`munmap`, with the specific goal of testing allocators targeting Linux under Miri.

This supports `mmap` with `MAP_PRIVATE|MAP_ANONYMOUS`, and `PROT_READ|PROT_WRITE`, and explicitly does not support `MAP_SHARED` (because that's asking for MMIO) as well as any kind of file mapping (because it seems like nobody does `MAP_PRIVATE` on files even though that would be very sensible). And (officially) we don't support `MAP_FIXED`, so we always ignore the `addr` argument.

This supports `mremap` only when the implementation is allowed to move the mapping (so no `MREMAP_FIXED`, no `MREMAP_DONTUNMAP`, and required `MREMAP_MAYMOVE`), and also when the entirety of a region previously mapped by `mmap` is being remapped.

This supports `munmap` but only when the entirety of a region previously mapped by `mmap` is unmapped.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc
Projects
None yet
Milestone
0.4
Development

No branches or pull requests
1 participant
@catamorphism