This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: symtab/454: "DW_FORM_strp pointing outside of .debug_str section"
- From: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 21 Jan 2004 04:58:01 -0000
- Subject: Re: symtab/454: "DW_FORM_strp pointing outside of .debug_str section"
- Reply-to: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
The following reply was made to PR external/454; it has been noted by GNATS.
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: sje@cup.hp.com
Cc: gdb-gnats@sources.redhat.com, is@notochord.com
Subject: Re: symtab/454: "DW_FORM_strp pointing outside of .debug_str section"
Date: Tue, 20 Jan 2004 23:50:13 -0500 (EST)
Hi Steve,
My procedure is to change the bug from "open" to "feedback", along with
a note that says: "Hello, I am cleaning up old gdb bug reports and I'm
looking at your gdb PR from $LONG_TIME_AGO. It's working fine for me
now with $GDB_CURRENT and blah blah. Can you check and see if it's
working on your system with $GDB_CURRENT?"
Then wait 30 days. If there is no answer after 30 days, change the PR
from "feedback" to "closed", with another note that says "it works for
me, I haven't heard from you, I'm going ahead and closing the PR".
It's important to put some context in the note because the original
submitter has usually forgotten all about the contents of the PR
after two years. Plus I want to be polite and show some care to our
users.
Roughly 90% of the time, the 30 days go by and we don't hear anything
back. 8% of the time, the original submitter says "thanks, it works for
me now". And 2% of the time, there is still an issue.
Michael C
GDB QA Guy