Closed calvin2021y closed 7 months ago
17.0.6
Sorry, the backtrace itself doesn't help much for being able to fix the issue - we would need a way to actually reproduce the error as well.
In order to do that, you can add the linker argument -Wl,--reproduce=repro.tar
, which produces a file repro.tar
which contains all input files. By sharing this file somehow, we should be able to reproduce exactly this scenario, hopefully being able to reproduce the error in order to actually analyze and potentially fix it.
File size too big to upload after compressed, can you message me your email I will send it to you ?
My email is martin@martin.st - although I'm not a fan of very large attachments in the mail (how large is it?) if possible to transfer otherwise - are you able to upload it somewhere temporarily?
Would it be possible to compress the tar file?
sorry for late reply, I just email to you mailbox with attachment repro.tar.gz.
sorry for late reply, I just email to you mailbox with attachment repro.tar.gz.
I haven't received that mail, sorry. (I did check the spam folders.) How big is the attachment? Is it possible to upload/transfer it via some file sharing service?
Not sure why you are not get it, my mail server said it send success.
It is 28M after gzip -9
, now I use tar -cJf repro.tar.xz repro.tar
.
github not allow upload .xz
file, so I rename it to repro.tar.gz
, after download you may need rename it to repro.tar.xz
before decompress
Not sure why you are not get it, my mail server said it send success.
It is 28M after
gzip -9
, now I usetar -cJf repro.tar.xz repro.tar
.github not allow upload
.xz
file, so I rename it torepro.tar.gz
, after download you may need rename it torepro.tar.xz
before decompress
Thanks, I got this now, and I can reproduce the issue. It doesn't show up when running with address sanitizer, but it does show up in regular builds. So not very clear what is wrong, but I should be able to take it from here, thanks for the report and reproducer!
I've analyzed the issue and filed an upstream report for it now: https://github.com/llvm/llvm-project/issues/78591
Thanks for the hard work.
A prerelease with LLVM 18.1.0 RC 1 is out now, at https://github.com/mstorsjo/llvm-mingw/releases/tag/20240130, where this issue should be fixed.
thanks for the great work. I will test and update next week.
confirm fixed with the library build by clang-17.