Skip to content

Valgrind errors on regex! macro usage #13969

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

Closed
KokaKiwi opened this issue May 6, 2014 · 3 comments
Closed

Valgrind errors on regex! macro usage #13969

KokaKiwi opened this issue May 6, 2014 · 3 comments

Comments

@KokaKiwi
Copy link

KokaKiwi commented May 6, 2014

Using regex! macro on Rust program cause Valgrind output many errors:

https://gist.github.com/KokaKiwi/11559159 (I don't paste it here because Valgrind output a lot of errors)

My rustc version:

sh-4.3$ rustc --version
rustc 0.11-pre-nightly (abdacec 2014-05-04 23:16:40 -0700)
host: x86_64-unknown-linux-gnu
alexcrichton added a commit to alexcrichton/rust that referenced this issue May 6, 2014
While speedier to not perform initialization, these calls to mem::init() are
causing valgrind errors when using compiled macros.

Closes rust-lang#13969
@KokaKiwi
Copy link
Author

KokaKiwi commented Aug 1, 2014

Just update the issue because I found some memory leaks on regex! example shown on regex crate documentation.
Actually, it seems to happen with named captures, but I'm not sure.
Here a gist I made with valgrind output: https://gist.github.com/KokaKiwi/86a3ca97dff3bc7133d0

I just updated the issue instead of creating a new one as it seems to me to be related (as it speaks about both regex and valgrind)

@alexcrichton
Copy link
Member

cc @BurntSushi

@steveklabnik
Copy link
Member

Regex has been moved out of tree.

bors added a commit to rust-lang-ci/rust that referenced this issue Feb 13, 2023
…kril

Use workspace.dependencies to declare local dependencies
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

Successfully merging a pull request may close this issue.

3 participants