FS#79685 - [android-tools] 34.0.4-1 breaks fastboot

Attached to Project: Arch Linux
Opened by Luca Weiss (z3ntu) - Thursday, 14 September 2023, 08:14 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:19 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Anatol Pomozov (anatolik)
Filipe Laíns (FFY00)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

After upgrading android-tools from 34.0.1-3 to 34.0.4-1, "fastboot flash super super.img" doesn't work anymore.

$ fastboot flash super images/super.img
terminate called after throwing an instance of 'std::out_of_range'
what(): basic_string::compare: __pos (which is 464) > this->size() (which is 0)
fish: Job 1, 'fastboot flash super images/sup…' terminated by signal SIGABRT (Abort)

This is reproducible every time. Downgrading to the previous version makes it work again.

Also reported 3 days ago on XDA (using Artix Linux and not Arch directly though):
https://forum.xda-developers.com/t/some-std-out_of_range-error-with-fastboot-on-linux.4626285/

Additional info:
* android-tools 34.0.4-1

Steps to reproduce:
fastboot flash super super.img (for reference my super.img is ~4GB and flashes in 6 parts (1/6 -> 6/6))
This task depends upon

Closed by  Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:19 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/archlinux/p ackaging/packages/android-tools/issues/4
Comment by Toolybird (Toolybird) - Thursday, 14 September 2023, 21:52 GMT
This doesn't appear to be an Arch packaging issue. You'll likely have better luck reporting the problem upstream. Please let us know what you find out.
Comment by q rty (q234rty) - Tuesday, 03 October 2023, 09:38 GMT
I believe this particular error is enabled by -Wp,-D_GLIBCXX_ASSERTIONS in the devtools makepkg.conf, I guess that flag is not there in google's build system?
Comment by Toolybird (Toolybird) - Wednesday, 04 October 2023, 06:00 GMT
Merging  FS#79847  here.
Comment by H. Cristiano Alves Machado (mccurly) - Thursday, 09 November 2023, 19:35 GMT
Hello to all.

This is still present with android-tools-34.0.4-3. I must say my technical skills are very limited. Nevertheless, if downgrading to previous android-tools-33.0.3-3, it fixes my problem. (I don't know at what expense, but for the moment it seems that I can use fastboot as usual).

Can anyone of acknowledge that this issue is still there?

Thank you.
Comment by loqs (loqs) - Friday, 10 November 2023, 14:46 GMT
Perhaps upstream might be more interested if a fix was provided. A backtrace would help locating where in the code the assertion is triggered.
Please provide a backtrace that includes debugging information. Please read the following links [1][2][3]. It's usually as simple as (with gdb installed):

$ coredumpctl gdb (then answer y when it asks "Enable debuginfod for this session?")
(gdb) set logging enabled
(gdb) bt (or bt full)

Then post gdb.txt

[1]: https://blogs.gnome.org/mcatanzaro/2021/09/18/creating-quality-backtraces-for-crash-reports/
[2]: https://wiki.archlinux.org/title/Debugging/Getting_traces
[3]: https://wiki.archlinux.org/title/Core_dump#Analyzing_a_core_dump

Loading...