Re: reading kernel dump - post gcc 3.1

[Craig Carey]

At 02\05\24 14:52 +0200 Friday, Georg-W. Koltermann wrote:
 >Hi,
 >
 >I got a couple of kernel panics recently, some of them "buffer not
 >locked". I would like to know how I can get more information out of the
 >dump.
 >
 >The system's gdb does not like the dump format any more, see also
 >bin/38236.  There is an advertised workaround in that pr of using gdb52,
 >but I couldn't get that to work ("not a core dump: File format not
 >recognized").
 >
 >Am I missing something? How do you guys read your dumps?
 >


There are online articles on how to get and read kernel panic dumps, at
these webpages. Also I copy parts views the articles.

http://www.onlamp.com/pub/a/bsd/2002/03/21/Big_Scary_Daemons.html
http://www.onlamp.com/pub/a/bsd/2002/03/21/Big_Scary_Daemons.html?page=2
System Panics, Part 1: Preparing for the Worst (21 March 2002),
  by Mr. M. Lucas

Add: options DDB makeoptions DEBUG=-g to config file.
A large enough swap file is needed for the dump.
Specify in /etc/rc.conf:  dumpdev="/dev/ad0s4b", the dumpdir may be
specified to be /var/crash.
Read savecore(8).

http://www.onlamp.com/pub/a/bsd/2002/04/04/Big_Scary_Daemons.html
http://www.onlamp.com/pub/a/bsd/2002/04/04/Big_Scary_Daemons.html?page=2
System Panics, Part 2: Recovering and Debugging (4 April 2002)

savecore(8) should copy a dump of the crashed kernel to /var/crash and
created files kernel.0 and vmcore.0.

gdb -k kernel.0 vmcore.0



__
Craig Carey


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: find(1) -regex/-iregex

[Craig Carey]

Can an  -iname  option be provided. Then the FreeBSD find would be
more like GNU find, and lines like this could be written:

find /msdos-disk -iname "*txt" | xargs -n 1 ls -l

I am doubtful that the -regexp needs to be inferior to the the
-egrep option. What software would break: it was said that there is
no regexp?. There are opinions around saying that egrep is better
than grep.

What is the -E option: perhaps this?:   -eregex

Suppose it is case sensitive. Then it could be
  -eiregex  or  -ieregex  or  -eregexi

I hope for no regex if there is no '-iname' feature. [It would be
nice if the advanced regexes settled onto the Perl regex, e.g.
perhaps throughout all utilities. -pregex ]




At 21-02-01 14:12 +0900 Wednesday, Akinori MUSHA wrote:
 >At Wed, 21 Feb 2001 12:35:09 +0900,
 >Daniel C. Sobral wrote:
 >> I'm not familiar with find sources, but it seems to me you execute
 >> regcomp() for each file name to be compared? If so... change that! :-)
 >> Regcomp() does expensive setup so that regexec() can be run
 >> inexpensively many times over.
 >
 >Indeed.  I'll do it soon, thanks.
 >
 >> You forgot -E (use extended regexp syntax), and the example you show
 >> above is extended regexp syntax, not basic regexp syntax.
 >
 >Noted.
 >
...

What about improving 'ls' too?: can there be an option so that it
refuses to list any information about directories (useful in the
above example). Also, is there any plan to stop the wastage of
space in the central columns of "ls"'s output, where it lists
uninteresting information. Maybe a '-p' option, like GNU 'ls'
has.






E-mail: Craig Carey <[EMAIL PROTECTED]>  (backup [EMAIL PROTECTED])
Auckland, NZ. |  Snooz Metasearch: http://www.ijs.co.nz/info/snooz.htm



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message