-
Notifications
You must be signed in to change notification settings - Fork 387
python abort with libmamba 2.0.5+ #3809
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
Comments
Also, I believe I saw this with earlier 2.0.X releases, but I don't have details. |
Hi, mamba 2.0.6 was marked as broken and the packages have been removed from conda-forge. Can you confirm you still have the issue with mamba 2.0.5? |
Hmm, I don't think that's quite it. It does seem like that code would attempt an out of range index lookup if parse() were passed "#". But that's not what's happening here. I recompiled libmamba with -O0 and I think I have better debug info. abort is happening at split_version_and_build:459:
The string that was passed in was " 1.7.1 py27_0". After the strip() it's "1.7.1 py27_0". str.find_last_of(" =") returns 5 the position of the space. And then the final find_last_of('=') returns string::npos since str does not contain a '=' at this point. That was introduced by c6f2f24 by @Hind-M I'm not sure I can grok what mamba is trying to do at this point, so hopefully someone more familiar with the code can step in at this point. |
Anyone? |
Troubleshooting docs
Anaconda default channels
How did you install Mamba?
Other (please describe)
Search tried in issue tracker
abort
Latest version of Mamba
Tried in Conda?
Not applicable
Describe your issue
I'm working on updating libmamba to 2.0.X in Fedora and running into a very strange issue. First off, I have had to set
-DMAMBA_WARNING_AS_ERROR=OFF
to work around #3791 . When I go to build conda 25.1.1, python aborts in one of the tests:So I added a print to that:
and I see:
which seems pretty innocuous. If I then run in gdb I see:
at which point I seem to have garbage.
valgrind doesn't show any issues that I can see.
It doesn't appear to gcc 15 related as I can reproduce the same issue in F41 with gcc 14.
We compile with the following:
though the build is done in stages:
It looks like it's the
-D_GLIBCXX_ASSERTIONS
that is triggering the abort, but it does seem to be catching something very strange going on.mamba info / micromamba info
Logs
environment.yml
~/.condarc
The text was updated successfully, but these errors were encountered: