Re: speed-dreams-2.4.2: How to determine the cause of a SIGSEGV signal

2025-06-03 Thread Martin Gansser
have set %global _lto_cflags %{nil} as you suggested. [1] https://martinkg.fedorapeople.org/ErrorReports/gdb.txt Regards Martin -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.or

Fedora eln compose report: 20250604.n.0 changes

2025-06-03 Thread Fedora ELN Report
OLD: Fedora-eln-20250603.n.0 NEW: Fedora-eln-20250604.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 0 Dropped packages:0 Upgraded packages: 24 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of

Re: F42 Elections Voting is now Open!

2025-06-03 Thread Aoife Moloney via devel-announce
Hi everyone, The results of the F42 elections are in! You can view the results in the blog post[1] on the Fedora Community blog[2]. Congratulations to our newly elected representatives and thank you to all of our great candidates in this election cycle! Kindest regards, Aoife [1] https://commu

Re: speed-dreams-2.4.2: How to determine the cause of a SIGSEGV signal

2025-06-03 Thread Vitaly Zaitsev via devel
On 02/06/2025 12:09, Martin Gansser wrote: I have installed speed-dreams-2.4.2 and noticed that a SIGSEGV, segmentation fault Can you try building without LTO optimizations? %global _lto_cflags %{nil} -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) -- _

Re: speed-dreams-2.4.2: How to determine the cause of a SIGSEGV signal

2025-06-03 Thread Vitaly Zaitsev via devel
On 03/06/2025 11:13, Florian Weimer wrote: If you use RelWithDebInfo instead, as Martin suggested, you'll get a better debugging experience. On Fedora, you won't notice any difference between the Release and RelWithDebInfo build configurations, since Fedora's build flags already include the -

Re: speed-dreams-2.4.2: How to determine the cause of a SIGSEGV signal

2025-06-03 Thread Martin Gansser
the build section of the speed-dreams.spec file looks like this on my local build: "%build %cmake -DCMAKE_BUILD_TYPE:STRING=RelWithDebInfo \ -DCMAKE_SKIP_RPATH:BOOL=OFF\ -DOPTION_DEBUG:STRING=ON \ -DCMAKE_SHARED_LINKER_FLAGS="-W

Re: Observation: 'acpi=off' kernel param breaking BIOS installations

2025-06-03 Thread Hans de Goede
Hi Michal, On 3-Jun-25 12:51 PM, Michal Schorm wrote: > Thanks for the insight ! > > I still wonder why the 'acpi=on' helped on the one machine. > Because it made a difference, I assume the 'acpi=on' is a different > value than the compiled-in default. > > I tried to look up what the default is.

Re: speed-dreams-2.4.2: How to determine the cause of a SIGSEGV signal

2025-06-03 Thread Miroslav Suchý
Dne 02. 06. 25 v 1:40 odp. Martin Gansser napsal(a): speed-dreams-debuginfo-2.4.2-1.fc42.x86_64 is already installed. Regards Martin No need to install it locally with debuginfod. See https://fedoraproject.org/wiki/Debuginfod and https://developers.redhat.com/blog/2019/10/14/introducing-debu

Fedora eln compose report: 20250603.n.0 changes

2025-06-03 Thread Fedora ELN Report
OLD: Fedora-eln-20250602.n.0 NEW: Fedora-eln-20250603.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 0 Dropped packages:0 Upgraded packages: 20 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of

Re: rpm 4.1 x 4.20 and custom debuginfo packages

2025-06-03 Thread Jiri Vanek
On 6/3/25 11:48, Michal Domonkos wrote: On Fri, May 30, 2025 at 05:12:41PM +0200, Jiri Vanek wrote: We had recently changed how we handle debuginfo in JDK: https://src.fedoraproject.org/rpms/java-latest-openjdk/pull-request/147#request_diff Main change is, that we create debuginfo manually. U

Re: Observation: 'acpi=off' kernel param breaking BIOS installations

2025-06-03 Thread Michal Schorm
Thanks for the insight ! I still wonder why the 'acpi=on' helped on the one machine. Because it made a difference, I assume the 'acpi=on' is a different value than the compiled-in default. I tried to look up what the default is. I looked here: https://src.fedoraproject.org/rpms/kernel/blob/raw

Re: rpm 4.1 x 4.20 and custom debuginfo packages

2025-06-03 Thread Jiri Vanek
hi! That would be very long story... JDK have feature of jlink. This can link a native image from only really needed subset of jdk, and your applciation. To do this, it was using jmod files. which contained copy of jdk "prepared" for jlinking. The https://openjdk.org/jeps/493 allowed to do th

Re: F43 Change Proposal: Package specific RPM Macros For Build Flags (system-wide)

2025-06-03 Thread Michal Schorm
On Tue, Jun 3, 2025 at 10:18 AM Petr Pisar wrote: > > V Mon, Jun 02, 2025 at 09:40:55PM +0100, Aoife Moloney via devel-announce > napsal(a): > > The proposed macros for adding new flags are: > > > > %_pkg_extra_cflags > > %_pkg_extra_cxxflags > > %_pkg_extra_fflags > > %_pkg_extra

Re: Observation: 'acpi=off' kernel param breaking BIOS installations

2025-06-03 Thread Hans de Goede
Hi Michal, On 3-Jun-25 11:35 AM, Michal Schorm wrote: > On Mon, Jun 2, 2025 at 4:09 PM Hans de Goede wrote: >> I'm not sure why you are specifying apci=off in the first place? > > On the system where I started, I met some ACPI related errors in the > kernel ring buffer. Firmware ACPI tables oft

Re: rpm 4.1 x 4.20 and custom debuginfo packages

2025-06-03 Thread Michal Domonkos
On Fri, May 30, 2025 at 05:12:41PM +0200, Jiri Vanek wrote: > We had recently changed how we handle debuginfo in JDK: > https://src.fedoraproject.org/rpms/java-latest-openjdk/pull-request/147#request_diff > Main change is, that we create debuginfo manually. Unluckily it was > developed with rpm 4.

Fedora rawhide compose report: 20250603.n.0 changes

2025-06-03 Thread Fedora Rawhide Report
OLD: Fedora-Rawhide-20250602.n.0 NEW: Fedora-Rawhide-20250603.n.0 = SUMMARY = Added images:14 Dropped images: 0 Added packages: 3 Dropped packages:1 Upgraded packages: 70 Downgraded packages: 0 Size of added packages: 993.37 KiB Size of dropped packages

Re: Observation: 'acpi=off' kernel param breaking BIOS installations

2025-06-03 Thread Michal Schorm
On Mon, Jun 2, 2025 at 4:09 PM Hans de Goede wrote: > I'm not sure why you are specifying apci=off in the first place? On the system where I started, I met some ACPI related errors in the kernel ring buffer. Disabling the problematic functionality often works as a good starting ground for me when

Re: rpm 4.1 x 4.20 and custom debuginfo packages

2025-06-03 Thread Florian Weimer
* Jiri Vanek: > Hi Florian, thanx a lot for kind reply! > > I saw the wrapper you have, and found it quite intensive. I was trying much > more simple workarounds, and also similar macro redefinition, but withotu > success. > > I'm, not sure I need any redefinition at all. The only thing I know i

Re: speed-dreams-2.4.2: How to determine the cause of a SIGSEGV signal

2025-06-03 Thread Florian Weimer
* Martin Gansser: > i think the current backtrace log [1] is also useless. > [1] ]https://martinkg.fedorapeople.org/ErrorReports/gdb2.txt > > Yes, i used on the koji buidl this Option: > '-DCMAKE_BUILD_TYPE:STRING=Release' If you use RelWithDebInfo instead, as Martin suggested, you'll get a bet

Re: rpm 4.1 x 4.20 and custom debuginfo packages

2025-06-03 Thread Jiri Vanek
Hi Florian, thanx a lot for kind reply! I saw the wrapper you have, and found it quite intensive. I was trying much more simple workarounds, and also similar macro redefinition, but withotu success. I'm, not sure I need any redefinition at all. The only thing I know is that rpm 4.1 is ignoring

Re: rpm 4.1 x 4.20 and custom debuginfo packages

2025-06-03 Thread Jiri Vanek
I have incorrectly stated "I'm, not sure I need any redefinition at all". it is not precisse. It seems tah in 4.1 the custom debuginfo packages needed the debuginfo enabled, however the debuginfo macros redefined to nil. That is what pointed me to search for debuginfo macro refeiniton and to

Re: F43 Change Proposal: Package specific RPM Macros For Build Flags (system-wide)

2025-06-03 Thread Petr Pisar
V Mon, Jun 02, 2025 at 09:40:55PM +0100, Aoife Moloney via devel-announce napsal(a): > The proposed macros for adding new flags are: > > %_pkg_extra_cflags > %_pkg_extra_cxxflags > %_pkg_extra_fflags > %_pkg_extra_ldflags > Does the leading underscore have any purpose? AFAIK RPM m

Re: speed-dreams-2.4.2: How to determine the cause of a SIGSEGV signal

2025-06-03 Thread Martin Gansser
maybe the next steps helps, i am not a debugging specialist. Thread 1 "speed-dreams-2" received signal SIGSEGV, Segmentation fault. 0x7fffb11687dc in ?? () (gdb) bt full #0 0x7fffb11687dc in ??? () #1 0x7fffdb60 in ??? () #2 0x77a90592 in _int_free (av=, p=, have_lock=