All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruno Vidal <bruno_vidal@hpfrcu03.france.hp.com>
To: "parisc-linux@lists.parisc-linux.org"
	<parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] vmlinux header for savecrash.
Date: Tue, 22 Jan 2002 10:20:59 +0100	[thread overview]
Message-ID: <3C4D2EFB.F82671C2@admin.france.hp.com> (raw)
In-Reply-To: 20020121202539.994A5482A@dsl2.external.hp.com

[-- Attachment #1: Type: text/plain, Size: 1736 bytes --]

	Sorry, but on my system, fgrep gives nothing
(and by using strings, I found nothing also). And I
can't use dmesg buffer, because by definition it is a buffer,
so after running sometime, the palo boot strings is not
in the buffer anymore. Some new ideas ?

	Thanks.

Grant Grundler wrote:
> 
> Bruno Vidal wrote:
> > As I said few days ago, I've a dump driver ready.
> > Now I'm working on a savecrash command. It works fine
> > for the dump, but I need to save with the dump some
> > informations like the running kernel at dump time.
> 
> Bruno - this is great!
> 
> > So in the dump I've got this informations:
> > utsname_release and utsname_version. Now, how can
> > I found the right kernel in /boot ? In other
> > word, how can I retrieve utsname informations in a
> > binary file (without system.map and gdb) ?
> 
> A couple of ideas/hacks:
> o assume it's /boot/System.map + /boot/vmlinux. Tell people if they
>   want to use dump/savecrash, that's what they have to do.
> 
> o assume it's in /boot. Use fgrep to find the matching strings.
>   Something like
>         #!/bin/sh
>         cd /boot
>         for i in *
>         do
>                 fgrep $1 $i > /dev/null 2>&1
>                 if [ $? -eq 0 ]
>                 then
>                         echo $i
>                         exit 0
>                 fi
>         done
>         exit 1
> 
> The case that /boot might not be mounted could cause problems.
> 
> Since klogd seems to want System.map, perhaps savecrash could use
> the same heuristics to find the "right" System.map.
> See Documentation/oops-tracing.txt for more details.
> 
> hth,
> grant

-- 
	Vidal Bruno, (770-4271)
        SSD-HA Team, HP-UX & LINUX Support
	bruno_vidal@admin.france.hp.com

[-- Attachment #2: Card for Bruno Vidal --]
[-- Type: text/x-vcard, Size: 386 bytes --]

begin:vcard 
n:Bruno;VIDAL
tel;fax:01-69-82-60-14
tel;work:01-69-29-42-71
x-mozilla-html:TRUE
url:www.france.hp.com
org:Solution Center
version:2.1
email;internet:bruno_vidal@hp.com
title:Expert Logiciel Environnement Haute Disponibilité
adr;quoted-printable:;;HP France=0D=0A;Z.A de Courtaboeuf;1 Av. du Canada;91947 Les Ulis cedex;France
x-mozilla-cpt:;26208
fn:VIDAL Bruno
end:vcard

  reply	other threads:[~2002-01-22  9:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-21 17:45 [parisc-linux] vmlinux header for savecrash Bruno Vidal
2002-01-21 20:25 ` Grant Grundler
2002-01-22  9:20   ` Bruno Vidal [this message]
2002-01-22  9:55     ` Enrik Berkhan
2002-01-22 12:25       ` Bruno Vidal
2002-01-22 15:11         ` Enrik Berkhan
2002-01-22 15:13         ` Matthew Wilcox
2002-01-22 12:05     ` James P. Kinney III
2002-01-22 17:45     ` Grant Grundler
2002-01-22 17:53       ` Randolph Chung
2002-01-22 17:59         ` Bruno Vidal
2002-01-22 17:55       ` Bruno Vidal
2002-01-22 18:11         ` Randolph Chung
2002-01-22 18:34         ` Grant Grundler
2002-01-22  0:43 ` James P. Kinney III
  -- strict thread matches above, loose matches on Subject: below --
2002-01-07  2:58 [parisc-linux] installation problems on an A500 Matthias Klose
2002-01-07  3:46 ` Grant Grundler
2002-01-22 19:59   ` [parisc-linux] vmlinux header for savecrash Paul Bame
2002-01-23  2:13     ` Grant Grundler
2002-01-23 10:23       ` Andreas Deresch
2002-01-25  6:30         ` Grant Grundler
2002-01-23  8:57     ` Enrik Berkhan
2002-01-23  9:29       ` phi 4369

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=3C4D2EFB.F82671C2@admin.france.hp.com \
    --to=bruno_vidal@hpfrcu03.france.hp.com \
    --cc=parisc-linux@lists.parisc-linux.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.