<sjg1>
milkylainen_: Do you think it is a bug? Can you recreate it in a 10-line program?
akaWolf has quit [Read error: Connection reset by peer]
vagrantc has quit [Quit: leaving]
akaWolf has joined #u-boot
camus has quit [Ping timeout: 260 seconds]
camus has joined #u-boot
agust has joined #u-boot
rfried has quit [*.net *.split]
kallisti5 has quit [*.net *.split]
kallisti5 has joined #u-boot
marex has quit [*.net *.split]
apalos has quit [*.net *.split]
cyrozap has quit [*.net *.split]
kmaincent has quit [*.net *.split]
elafon has quit [*.net *.split]
elafon has joined #u-boot
cyrozap has joined #u-boot
marex has joined #u-boot
kmaincent has joined #u-boot
apalos has joined #u-boot
guillaume_g has joined #u-boot
fdanis_away is now known as fdanis
tre has joined #u-boot
tambarus has joined #u-boot
fdanis is now known as fdanis_away
sstiller has joined #u-boot
<milkylainen_>
sjg1: I always think that if a program segfaults on parsing input = bug. So yes. :) But sadly, I cannot recreate it. Still in the dark on what's causing it.
<milkylainen_>
I still suspect some kind of reloc section mishandled into an *abs* section. I think the ld.bfd bug is something like "ld.bfd somewhat blindly assumes an alloc has been made for the output section of certain types. But the output and input parsing differ in their handling. So input doesn't do an alloc and output blindly assumes it has been made".
<milkylainen_>
And if they end up in this scenario you have a SEGV in the output generation.
<milkylainen_>
Which was why the hacks for .reloc in coff where written in the first place. But those hacks are just plain ugly.
<milkylainen_>
Because they only cover one type of scenario of the mismatch.
fdanis_away is now known as fdanis
matthias_bgg has joined #u-boot
lucaceresoli has joined #u-boot
michalkotyla has joined #u-boot
sszy has joined #u-boot
monstr has joined #u-boot
camus1 has joined #u-boot
camus has quit [Ping timeout: 268 seconds]
camus1 is now known as camus
camus has quit [Ping timeout: 260 seconds]
camus has joined #u-boot
mmu_man has joined #u-boot
tnovotny has joined #u-boot
brujah has joined #u-boot
smartin has joined #u-boot
mmu_man has quit [Ping timeout: 265 seconds]
redbrain has joined #u-boot
mmu_man has joined #u-boot
camus has quit [Remote host closed the connection]
camus has joined #u-boot
mmu_man has quit [Ping timeout: 265 seconds]
alpernebbi has quit [Ping timeout: 264 seconds]
alpernebbi has joined #u-boot
mckoan_ is now known as mckoan
mmu_man has joined #u-boot
vigneshr has joined #u-boot
torez has joined #u-boot
samekh has joined #u-boot
mmu_man has quit [Ping timeout: 250 seconds]
tre has quit [Remote host closed the connection]
FredO2 has quit [Remote host closed the connection]
FredO2 has joined #u-boot
Xogium has joined #u-boot
<Xogium>
hi guys… Using u-boot 2021.01 on stm32f769 discovery… I burned default config u-boot onto the internal flash, copied u-boot.bin as per what the buildroot instructions for stm32f469 did -- there is no config for f769 in br
<Xogium>
set console to 115200n8, connected to the st-link probe and… nothing
<Xogium>
I don't see any message on the serial console
<Xogium>
can someone give a hand with this ?
<Xogium>
is u-boot supposed to be silent ?
<Xogium>
I don't know in what state my board is other than red and green leds are fixed, and that's all
samekh has quit [Ping timeout: 264 seconds]
samekh has joined #u-boot
swiftgeek has quit [Ping timeout: 260 seconds]
<sjg1>
milkylainen_: I wonder if you can pair down the U-Boot link command until it is just one file that still causes the problem?
swiftgeek has joined #u-boot
Xogium has left #u-boot [leaving channel]
torez has quit [Ping timeout: 250 seconds]
mmu_man has joined #u-boot
gsz has joined #u-boot
torez has joined #u-boot
sstiller has quit [Quit: Leaving]
michalkotyla has quit [Quit: michalkotyla]
monstr has quit [Remote host closed the connection]
milkylainen has joined #u-boot
vagrantc has joined #u-boot
guillaume_g has quit [Quit: Konversation terminated!]