lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20060830145300.7d728f6c.rdunlap@xenotime.net>
Date:	Wed, 30 Aug 2006 14:53:00 -0700
From:	"Randy.Dunlap" <rdunlap@...otime.net>
To:	piet@...elane.com
Cc:	vgoyal@...ibm.com, George Anzinger <george@...dturkeyranch.net>,
	Andrew Morton <akpm@...l.org>,
	Discussion
	 "list for crash utility usage, maintenance and development" 
	<crash-utility@...hat.com>, kgdb-bugreport@...ts.sourceforge.net,
	Subhachandra Chandra <schandra@...elane.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] [Crash-utility] Patch to use gdb's bt in crash - works
 great with kgdb! - KGDB in Linus Kernel.

On Wed, 30 Aug 2006 14:41:32 -0700 Piet Delaney wrote:

> On Wed, 2006-08-30 at 16:40 -0400, Vivek Goyal wrote:
> > On Wed, Aug 30, 2006 at 12:35:21PM -0700, Piet Delaney wrote:
> > > > 
> > > > Simple question -- and to be quite honest with you -- I don't
> > > > understand why you wouldn't want to simply use gdb alone
> > > > in this case?
> > > 
> > > I don't see any reason for core file not to be read correctly by
> > > gdb. It's convenient to use gdb directly sometimes, for example
> > > while using the ddd GUI.
> > > 
> > 
> > You can run gdb to open core files as of today but the debugging
> > capability will be limited. For ex. kernel core headers have the info
> > of linearly mapped region only and they don't contain the virt address
> > info of non-linearly mapped regions. So one can not debug the non-linearly
> > mapped regions like modules.
> 
> Amit's modified gdb might help for that problem. I haven't used
> it but it allows gdb to load debug information about modules. You
> can also use a script Amit wrote to explicitly load module info
> into stock gdb; that also might work with kernel core files.
> 
> > 
> > > kgdb isn't having any problems with kernel threads back traces.
> > > The kernel objects are tweaked with dwarf code, but I see no
> > > problem with using the same paradigm with crash. Works great.
> > > 
> > 
> > Can you give some more details on what do you mean by kernel objects
> > are tweaked with dwarf code. 
> 
> Attached is the cfi_annotations.patch patch from the kgdb-2.6.16 patch
> which is part of the kgdb patch series. I believe George Anzinger used 
> a similar dwarf patch in the 2.6 mm series patches that Andrew provided.
> I think Tom Rini wrote both of them. 

ENOPATCH

---
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ