From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Roland McGrath <roland@redhat.com>
Cc: Wenji Huang <wenji.huang@oracle.com>, systemtap@sources.redhat.com
Subject: Re: Bug: duplicate marker entry in Modules.marker
Date: Thu, 20 Mar 2008 01:05:00 -0000 [thread overview]
Message-ID: <20080320010521.GA7633@Krystal> (raw)
In-Reply-To: <20080319080227.6CC9026F9A2@magilla.localdomain>
* Roland McGrath (roland@redhat.com) wrote:
> I modelled Module.markers generation on Module.symvers generation.
> How does it deal with the problem?
Is is me or they seem to detect, for each symbol, if it has changed and
they overwrite the original one ?
We could do the same with markers I guess. After having sorted them, we
could determine, for each, if there was an entry in the original file
and modify it if needed.
Separate concern : I would really like to have some kind of format
string coherency verification in there : when we extract the markers
from a build tree, we should be able to check that all the markers with
the same name have the same format string. Otherwise the incoherency
will only be detected at runtime.
Regards,
Mathieu
--
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2008-03-20 1:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 16:00 Markers usage Mathieu Desnoyers
2008-01-29 16:15 ` Frank Ch. Eigler
2008-03-19 3:02 ` Bug: duplicate marker entry in Modules.marker Wenji Huang
2008-03-19 3:07 ` Roland McGrath
2008-03-19 7:53 ` Wenji Huang
2008-03-19 8:03 ` Roland McGrath
2008-03-20 1:05 ` Mathieu Desnoyers [this message]
2008-03-20 8:29 ` Roland McGrath
2008-03-20 8:38 Roland McGrath
2008-03-20 9:02 ` Wenji Huang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080320010521.GA7633@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=roland@redhat.com \
--cc=systemtap@sources.redhat.com \
--cc=wenji.huang@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).