On Fri, 31 May 2024 at 13:39, Mark Wielaard wrote:
>
> Hi Luca,
>
> On Thu, 2024-05-30 at 11:45 +0100, Luca Boccassi wrote:
> > On Tue, 14 May 2024 at 22:18, Mark Wielaard wrote:
> > > Not a fan of json, feels very un-ELF. But it is what it is. The patch
> >
On Tue, 14 May 2024 at 22:18, Mark Wielaard wrote:
>
> Hi Luca,
>
> On Fri, May 10, 2024 at 10:58:02PM +0100, luca.bocca...@gmail.com wrote:
> > Note that the webpage in the comment is not published yet,
> > it will be next week when the next systemd RC is tagged.
> > The document can be viewed ri
From: Luca Boccassi
Note that the webpage in the comment is not published yet,
it will be next week when the next systemd RC is tagged.
The document can be viewed right now on github at:
https://github.com/systemd/systemd/blob/main/docs/ELF_DLOPEN_METADATA.md
But the node ID and the string
On Tue, 20 Jun 2023 at 13:07, Mark Wielaard wrote:
>
> Hi Luca,
>
> On Mon, 2023-06-19 at 21:54 +0100, Luca Boccassi wrote:
> > > > Which does bring up the question why systemd-coredump isn't running
> > > in
> > > > the same mount space as the
ct from all the guests, so they are going to be in different
namespaces. And even when they are not, the original binary might be
long gone by the time it has a chance to run.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
On Mon, 2022-03-28 at 11:57 +0200, Mark Wielaard wrote:
> Hi Luca,
>
> On Sat, 2022-03-26 at 18:19 +0000, Luca Boccassi wrote:
> > > Already working on the updated script, the native type is exactly
> > > the
> > > approach I was taking, this works fine on
On Sat, 2022-03-26 at 16:57 +, Luca Boccassi wrote:
> On Sat, 2022-03-26 at 17:33 +0100, Mark Wielaard wrote:
> > Hi Luca,
> >
> > On Fri, Mar 25, 2022 at 02:55:14PM +, Luca Boccassi wrote:
> > > On Fri, 2022-03-25 at 15:47 +0100, Mark Wielaard wrote
On Sat, 2022-03-26 at 17:33 +0100, Mark Wielaard wrote:
> Hi Luca,
>
> On Fri, Mar 25, 2022 at 02:55:14PM +0000, Luca Boccassi wrote:
> > On Fri, 2022-03-25 at 15:47 +0100, Mark Wielaard wrote:
> > > > We have completely overlooked that, the note is created by a
&g
On Fri, 2022-03-25 at 15:47 +0100, Mark Wielaard wrote:
> Hi Luca,
>
> On Fri, 2022-03-25 at 13:52 +0000, Luca Boccassi wrote:
> > On Fri, 2022-03-25 at 14:39 +0100, Mark Wielaard wrote:
> > > But I noticed an issue on s390x fedora 36.
> > > This isn't j
On Fri, 2022-03-25 at 14:39 +0100, Mark Wielaard wrote:
> Hi Luca,
>
> On Fri, 2022-03-25 at 11:17 +0000, Luca Boccassi wrote:
> > On Fri, 2022-03-25 at 00:14 +0100, Mark Wielaard wrote:
> > > I took the elf.h update separately. Tweaked your patch a little and
> >
the first PoC that uses the spec in
Debian, for the systemd packages:
$ readelf --notes /usr/lib/systemd/systemd | grep Packaging
Packaging Metadata:
{"type":"deb","os":"debian","name":"systemd","architecture":"amd64","version":"250.4-1","debugInfoUrl":"https://debuginfod.debian.net"}
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
On Tue, 2021-11-30 at 12:25 +0100, Mark Wielaard wrote:
> Hi Luca,
>
> On Thu, 2021-11-25 at 17:02 +0000, Luca Boccassi via Elfutils-devel
> wrote:
> > +/* Packaging metadata as defined on
> > > https://systemd.io/COREDUMP_PACKAGE_METADATA/ */
> > > +#defi
On Sun, 2021-11-21 at 19:43 +, luca.bocca...@gmail.com wrote:
> From: Luca Boccassi
>
> As defined on: https://systemd.io/COREDUMP_PACKAGE_METADATA/
> this note will be used starting from Fedora 36. Allow
> readelf --notes to pretty print it:
>
> Note section [ 3]
On Sun, 2021-11-21 at 17:33 +0100, Mark Wielaard wrote:
> Hi Luca,
>
> On Fri, Nov 19, 2021 at 12:31:27AM +, luca.boccassi--- via
> Elfutils-devel wrote:
> > From: Luca Boccassi
> >
> > As defined on: https://systemd.io/COREDUMP_PACKAGE_METADATA/
> >
m. Being able to know at a glance to the journal exactly what
is borken, with version info, is extremely valuable to them.
Yes the version info might not be precise for a minority of use cases
that override the binary version with something different than the
source version, but that's fine as it's far and few, mostly affects
metapackages, and even then it can be documented clearly that the
reference is to the source version, not the binary one.
--
Kind regards,
Luca Boccassi
signature.asc
Description: This is a digitally signed message part
On Fri, 2021-05-14 at 12:41 +0200, Guillem Jover wrote:
> On Sat, 2021-04-10 at 13:38:31 +0100, Luca Boccassi wrote:
> > On Sat, 2021-04-10 at 13:29 +0100, Luca Boccassi wrote:
> > > After an initial discussion [0], recently we have been working on a new
> > > speci
On Thu, 2021-05-06 at 03:17 +0200, Mark Wielaard wrote:
> Hi Luca,
>
> On Tue, 2021-05-04 at 14:43 +0100, Luca Boccassi wrote:
> > On Fri, 2021-04-30 at 19:57 +0200, Mark Wielaard wrote:
> > > Is there a list of default keys (and their canonical spelling, upper-
> >
On Fri, 2021-04-30 at 19:57 +0200, Mark Wielaard wrote:
> Hi,
>
> On Sat, 2021-04-10 at 18:44 +, Zbigniew Jędrzejewski-Szmek wrote:
> > [I'm forwarding the mail from Luca who is not subscribed to fedora-
> > devel]
> > On Sat, Apr 10, 2021 at 01:38:31PM +0100
On Sat, 2021-04-10 at 13:29 +0100, Luca Boccassi wrote:
> Hello,
>
> Cross-posting to the mailing lists of a few relevant projects.
>
> After an initial discussion [0], recently we have been working on a new
> specification [0] to encode rich package-level metadata inside ELF
tools that parse core files and logs.
Tools for RPM and DEB (debhelper) integration are also available [3].
--
Kind regards,
Luca Boccassi
[0] https://github.com/systemd/systemd/issues/18433
[1] https://systemd.io/COREDUMP_PACKAGE_METADATA/
[2] https://fedoraproject.org/wiki/Changes/Package_informa
x61) BYTE(0x63)
BYTE(0x6b) BYTE(0x61) BYTE(0x67) BYTE(0x65)
BYTE(0x56) BYTE(0x65) BYTE(0x72) BYTE(0x73)
BYTE(0x69) BYTE(0x6f) BYTE(0x6e) BYTE(0x22)
BYTE(0x3a) BYTE(0x22) BYTE(0x31) BYTE(0x2e)
BYTE(0x33) BYTE(0x2d) BYTE(0x31) BYTE(0x22)
BYTE(0x7d) BYTE(0x0
21 matches
Mail list logo
