[uclibc-ng-devel] uclibc with gcc 8.3.1

[Ata, John (US)]

Hi all,

Has anyone successfully created a toolchain with the latest uClibc and gcc 
8.3.1?

Thanks,

John Ata, CISSP
Senior Principal Software Engineer
Electronics Systems
STOP Operating System Software 
Development

T 703-563-8115 | F 703-668-4359 | 
john@baesystems.com
http://www.baesystems.com/csp

[cid:image001.png@01D138BC.8E54E330][cid:image003.png@01D138BC.8E54E330][cid:image004.png@01D138BC.8E54E330][cid:image006.png@01D138BC.8E54E330]


___
devel mailing list
devel@uclibc-ng.org
https://mailman.uclibc-ng.org/cgi-bin/mailman/listinfo/devel

Re: [uclibc-ng-devel] Bug: Deadlock in malloc on ARMv6 with uClibc-ng + Thumb1 + NPTL

[Gyula FARKAS]

Hello,

We have managed to reproduce the issue with your binary.

Tested with (./deadlock 4 100):

- Raspberry Pi 1 with Raspbian Buster
- Raspberry Pi 3 with Raspbian Buster
- QEMU 4.2.0 on a Core i7-8650U Archlinux
- QEMU 4.2.0 on a Core i7-8700 Gentoo

Maybe you are using an older version of QEMU which does not have support 
for Multi-Threaded TCG? One single core machines/emulation the mutex 
deadlocks much less often. The occurrence depends on CPU speed and 
thread numbers.

You may need to increase the thread numbers (first argument) and 
iteration count (second argument) or even try to run several times.

Best regards,
Gyula FARKAS

On 2/21/20 1:30 PM, Waldemar Brodkorb wrote:
> Hi,
> Gyula FARKAS wrote,
> 
>> Hello,
>>
>> The segfault is from the missing command line arguments, which I did not 
>> check in sample app. Please run it as:
>>
>>  $ ./deadlock 4 100
> 
> Does it happen with the attached binary? I couldn't reproduce in
> Qemu.
> 
> best regards
>   Waldemar
> 
> 
> This email was scanned by Bitdefender
> 
___
devel mailing list
devel@uclibc-ng.org
https://mailman.uclibc-ng.org/cgi-bin/mailman/listinfo/devel

Re: [uclibc-ng-devel] Bug: Deadlock in malloc on ARMv6 with uClibc-ng + Thumb1 + NPTL

[Waldemar Brodkorb]

Hi,
Gyula FARKAS wrote,

> Hello,
> 
> The segfault is from the missing command line arguments, which I did not 
> check in sample app. Please run it as:
> 
> $ ./deadlock 4 100

Does it happen with the attached binary? I couldn't reproduce in
Qemu.

best regards
 Waldemar


deadlock
Description: Binary data
___
devel mailing list
devel@uclibc-ng.org
https://mailman.uclibc-ng.org/cgi-bin/mailman/listinfo/devel