[Pkg-xen-devel] Bug#1073913: FTBFS with OCaml 5.2.0 (Problem in C stubs)

Maximilian Engelhardt maxi at daemonizer.de
Sun Aug 25 21:25:20 BST 2024


Control: tags -1 + pending

On Fri, 21 Jun 2024 09:01:02 +0200 Stéphane Glondu <glondu at debian.org> wrote:
> > Your package FTBFS with OCaml 5.2.0 for the following reason:
> > 
> >   Problem in C stubs
> 
> Attached is a patch that fixes the issues. It should also work with the 
> version of OCaml currently in unstable.

Unfortunately the patch makes xen 4.17 compile in unstable, but it gives a 
segmentation fault when trying to run the binary:

root at host:~# /usr/lib/xen-4.17/bin/oxenstored --no-fork
Xen Storage Daemon, version 1.0
Segmentation fault

root at host:~# gdb --args /usr/lib/xen-4.17/bin/oxenstored --no-fork
GNU gdb (Debian 15.1-1) 15.1
Copyright (C) 2024 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/xen-4.17/bin/oxenstored...
Reading symbols from /usr/lib/debug/.build-id/6e/
2ee766ed4e47a311ca34cdd765bc82bf8943e8.debug...
(gdb) run
Starting program: /usr/lib/xen-4.17/bin/oxenstored --no-fork
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Xen Storage Daemon, version 1.0

Program received signal SIGSEGV, Segmentation fault.
0x00005555556654dd in do_some_marking ()
(gdb) bt
#0  0x00005555556654dd in do_some_marking ()
#1  0x00005555556657d5 in mark ()
#2  0x0000555555665eaf in major_collection_slice ()
#3  0x00005555556666e4 in stw_finish_major_cycle ()
#4  0x0000555555654c89 in caml_try_run_on_all_domains_with_spin_work ()
#5  0x0000555555666825 in caml_finish_major_cycle ()
#6  0x000055555565b2ba in gc_full_major_exn ()
#7  0x000055555565be34 in caml_gc_stat ()
#8  <signal handler called>
#9  0x00005555555b312a in camlXenstored.entry ()
#10 0x00005555555ac927 in caml_program ()
#11 <signal handler called>
#12 0x0000555555675e15 in caml_startup_common ()
#13 0x0000555555675e8f in caml_main ()
#14 0x00005555555ac352 in main ()
(gdb) quit

Fortunately upstream seems to have fixed the problem in newer versions of xen 
and I tested it does not occur with xen 4.19 which we will upload to 
experimental soon.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-xen-devel/attachments/20240825/f01c5a68/attachment-0001.sig>


More information about the Pkg-xen-devel mailing list