From: Enrik Berkhan <Enrik.Berkhan@planb.de>
To: Bruno Vidal <bruno_vidal@hpfrcu03.france.hp.com>
Cc: "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:55:53 +0100 [thread overview]
Message-ID: <20020122105553.A5510@electra.intern.planb.de> (raw)
In-Reply-To: <3C4D2EFB.F82671C2@admin.france.hp.com>
On Tue, Jan 22, 2002 at 10:20:59AM +0100, Bruno Vidal wrote:
> 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 ?
I think the correct way would be to use libbfd to achieve something
similar to the following in "shell notation":
| objdump -t vmlinux| grep " system_utsname"
102860c0 g O .data 00000186 system_utsname
^ start ^ size
| objdump --start-address=0x102860c0 --stop-address=0x10286246 vmlinux
...
102860c0 4c696e75 78000000 00000000 00000000 Linux...........
102860d0 00000000 00000000 00000000 00000000 ................
102860e0 00000000 00000000 00000000 00000000 ................
102860f0 00000000 00000000 00000000 00000000 ................
10286100 00286e6f 6e652900 00000000 00000000 .(none).........
10286110 00000000 00000000 00000000 00000000 ................
10286120 00000000 00000000 00000000 00000000 ................
10286130 00000000 00000000 00000000 00000000 ................
10286140 0000322e 342e3137 2d706131 31000000 ..2.4.17-pa11...
10286150 00000000 00000000 00000000 00000000 ................
10286160 00000000 00000000 00000000 00000000 ................
10286170 00000000 00000000 00000000 00000000 ................
10286180 00000023 3134204d 6f6e204a 616e2032 ...#14 Mon Jan 2
10286190 31203230 3a34323a 33352043 45542032 1 20:42:35 CET 2
102861a0 30303200 00000000 00000000 00000000 002.............
...
Using libbfd it should be feasible to read a "struct new_utsname"
from the binaries. Sorry, but don't have the time for a better
proof-of-concept than using objdump today.
Enrik
--
Enrik Berkhan plan b. GmbH
Rüppurrer Straße 4
+49-721-388582 (voice) 76137 Karlsruhe
+49-721-388581 (fax) Germany
next prev parent reply other threads:[~2002-01-22 9:55 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
2002-01-22 9:55 ` Enrik Berkhan [this message]
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=20020122105553.A5510@electra.intern.planb.de \
--to=enrik.berkhan@planb.de \
--cc=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.