🚀 go-pugleaf

--_000_55E352C95790B84FA0ACDB59FE48F13F75F12385chsys232sycamor_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

I'm using an older version of a cross-platform GDB build (7.0.1 based).  Ha=
ving to use the "find" command a lot, as I do, is a pain because it seem to=
 always have been broken and never fixed (?).  The problem is that "find" s=
ometimes works, but often returns bogus matches.  I came across an old dorm=
ant problem report, Bugzilla - Bug 11158 "find command returns bogus result=
s", but I've never seen any fixes for this.

So I took it upon myself to fix this, and after looking at the source code,=
 doing some debugging, and identifying multiple issues, I came to the concl=
usion that it's best to rewrite the function simple_search_memory() in gdb/=
target.c.  I did that and I believe it's now works properly.

I did look at the latest version, 7.4, and there is one minor change in tha=
t function which looks to be an attempt at a fix. I didn't try this out, bu=
t I have my doubts that this is a correct fix, nor does it address other is=
sues I noticed in the function.

Anyone interested in the getting my update?  I'd be happy to forward it.

BTW, I also would like to enhance "find" so that it doesn't just stop when =
it encounters an invalid region of memory, but skips past it (with a warnin=
g) if there is valid memory at a higher address within the specified range.=
  This would be really useful for scanning all of the heap memory in a proc=
ess, which is often disjoint with numerous gaps in between memory segments.=
  The current need to repeat the "find" many times with different ranges is=
 very awkward.  Any thoughts on this?

Best regards,
Ray

--_000_55E352C95790B84FA0ACDB59FE48F13F75F12385chsys232sycamor_
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=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"\@Batang";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* 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 .5in 1.0in .5in;}
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 all,<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>&nbsp;</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&#8217;m using an older version of a cross-platform GDB=
 build
(7.0.1 based). &nbsp;Having to use the &#8220;find&#8221; command a lot, as=
 I do, is
a pain because it seem to always have been broken and never fixed (?). &nbs=
p;The
problem is that &#8220;find&#8221; sometimes works, but often returns bogus
matches. &nbsp;I came across an old dormant problem report, Bugzilla &#8211=
;
Bug&nbsp;11158 &#8220;</span></font><font size=3D2 color=3Dblack face=3DHel=
vetica><span
style=3D'font-size:10.0pt;font-family:Helvetica;color:black'>find command r=
eturns
bogus results</span>&#8221;, but I&#8217;ve never seen any fixes for this.<=
o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DHelvetica><span
style=3D'font-size:10.0pt;font-family:Helvetica;color:black'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DHelvetica><span
style=3D'font-size:10.0pt;font-family:Helvetica;color:black'>So I took it u=
pon
myself to fix this, and after looking at the source code, doing some debugg=
ing,
and identifying multiple issues, I came to the conclusion that it&#8217;s b=
est
to rewrite the function simple_search_memory() in gdb/target.c. &nbsp;I did=
 that and
I believe it&#8217;s now works properly.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DHelvetica><span
style=3D'font-size:10.0pt;font-family:Helvetica;color:black'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DHelvetica><span
style=3D'font-size:10.0pt;font-family:Helvetica;color:black'>I did look at =
the
latest version, 7.4, and there is one minor change in that function which l=
ooks
to be an attempt at a fix. I didn&#8217;t try this out, but I have my doubt=
s that
this is a correct fix, nor does it address other issues I noticed in the
function.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DHelvetica><span
style=3D'font-size:10.0pt;font-family:Helvetica;color:black'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DHelvetica><span
style=3D'font-size:10.0pt;font-family:Helvetica;color:black'>Anyone interes=
ted in
the getting my update? &nbsp;I&#8217;d be happy to forward it. <o:p></o:p><=
/span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DHelvetica><span
style=3D'font-size:10.0pt;font-family:Helvetica;color:black'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DHelvetica><span
style=3D'font-size:10.0pt;font-family:Helvetica;color:black'>BTW, I also wo=
uld
like to enhance &#8220;find&#8221; so that it doesn&#8217;t just stop when =
it
encounters an invalid region of memory, but skips past it (with a warning) =
if
there is valid memory at a higher address within the specified range.&nbsp;=
 This
would be really useful for scanning all of the heap memory in a process, wh=
ich
is often disjoint with numerous gaps in between memory segments. &nbsp;The =
current need
to repeat the &#8220;find&#8221; many times with different ranges is very
awkward.&nbsp; Any thoughts on this?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DHelvetica><span
style=3D'font-size:10.0pt;font-family:Helvetica;color:black'><o:p>&nbsp;</o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DHelvetica><span
style=3D'font-size:10.0pt;font-family:Helvetica;color:black'>Best regards,<=
o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DHelvetica><span
style=3D'font-size:10.0pt;font-family:Helvetica;color:black'>Ray<o:p></o:p>=
</span></font></p>

</div>

</body>

</html>

--_000_55E352C95790B84FA0ACDB59FE48F13F75F12385chsys232sycamor_--