From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: backtrace support
Date: Sun, 28 Aug 2005 14:49:34 +0200 [thread overview]
Message-ID: <200508281449.34476.okuji@enbug.org> (raw)
In-Reply-To: <430A4263.1020103@inma.ucl.ac.be>
On Monday 22 August 2005 23:23, Vincent Guffens wrote:
> +# For kern_debug.mod
> +kern_debug_mod_OTHERDEP = kern/grub_debug_kern.sym
> +kern_debug_mod_SOURCES = kern/kern_debug.c
> +kern_debug_mod_CFLAGS = $(COMMON_CFLAGS)
I think it is a really good idea to make a variable for dependencies, but I
would suggest a different name for this. Can this be just
kern_debug_mod_DEPENDENCIES?
> +# take care of the configure arguments
> +
> +AC_ARG_WITH(debug, [ --with-debug enable some debug
mechanisms])
I think it would be better to use AC_ARG_ENABLE with --enable-debug, because
--with is used to specify external programs in autoconf.
> diff -ru -N -b -B grub2/gendebugkern.sh grub2-backtrace/gendebugkern.sh
> --- grub2/gendebugkern.sh 1970-01-01 01:00:00.000000000 +0100
> +++ grub2-backtrace/gendebugkern.sh 2005-08-22 18:47:48.000000000 +0200
> @@ -0,0 +1,14 @@
> +#!/bin/bash
Please do not use /bin/bash for portability. It should be:
#! /bin/sh
> +void EXPORT_FUNC(grub_register_debug_sym) (const char*, void*,
grub_size_t);
> +void EXPORT_FUNC(grub_unregister_debug_sym) (void *);
> +int EXPORT_FUNC(grub_print_debug_sym) (grub_addr_t);
> +void EXPORT_FUNC(grub_backtrace) (void);
Why do you need to export these functions? Are they used outside the kernel?
Okuji
next prev parent reply other threads:[~2005-08-28 13:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 21:23 backtrace support Vincent Guffens
2005-08-23 7:46 ` Vincent Pelletier
2005-08-28 12:49 ` Yoshinori K. Okuji [this message]
2005-08-29 9:47 ` Vincent Guffens
2005-08-28 13:47 ` Marco Gerards
2005-08-29 11:20 ` Vincent Guffens
2005-08-31 19:01 ` Marco Gerards
-- strict thread matches above, loose matches on Subject: below --
2005-08-18 20:22 Vincent Guffens
2005-08-18 20:58 ` Marco Gerards
2005-08-18 21:19 ` Vincent Guffens
2005-08-19 1:01 ` Yoshinori K. Okuji
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=200508281449.34476.okuji@enbug.org \
--to=okuji@enbug.org \
--cc=grub-devel@gnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.