Back porting of backtrace code into an older kernel
Dan Ben-Yaacov <[email protected]> Tue, 15 Dec 2009 11:40:07 +0200
| Newsgroups | gmane.linux.kernel.debugging |
|---|---|
| Message-ID | <844300ACDC2B4F41B224A576A9DFEA7B3B10C66870@il-ex01.ad.checkpoint.com> |
--===============1914649064659783323==
Content-Language: en-US
Content-Type: multipart/alternative;
boundary="_000_844300ACDC2B4F41B224A576A9DFEA7B3B10C66870ilex01adcheck_"
--_000_844300ACDC2B4F41B224A576A9DFEA7B3B10C66870ilex01adcheck_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi,
I've back ported the new KDB backtrace code into an older kernel.
My question regards both bb_spurious[] and bb_special_cases[] - I have a k=
ernel based on 2.6.18. I'm pretty sure that both somewhat mismatch my kerne=
l version and I'm pretty sure it affects quality of produced backtrace.
What should I look for in order of aligning both bb_spurious[] and bb_spec=
ial_cases[] with my kernel?
Dan
--_000_844300ACDC2B4F41B224A576A9DFEA7B3B10C66870ilex01adcheck_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Arial;
color:windowtext;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=3DEN-US link=3Dblue vlink=3Dpurple>
<div class=3DSection1>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Hi,<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>I’ve back ported the new KDB backtrace code into a=
n
older kernel.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>My question regards both bb_spurious[] and bb_spec=
ial_cases[]
– I have a kernel based on 2.6.18. I’m pretty sure that both so=
mewhat
mismatch my kernel version and I’m pretty sure it affects quality of =
produced
backtrace.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>What should I look for in order of aligning both bb_spur=
ious[]
and bb_special_cases[] with my kernel?<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Dan<o:p></o:p></span></font></p>
</div>
</body>
</html>
--_000_844300ACDC2B4F41B224A576A9DFEA7B3B10C66870ilex01adcheck_--
--===============1914649064659783323==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
kdb mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/kdb
--===============1914649064659783323==--