On Wednesday 12 April 2006 12:37, Some have written: > There seems to be tons of feedback with that bug report. [ Or similar. ]
I must get better at phrasing things then. There is a lot of feedback in the bug report. However, within the bug report there are still many questions which are never answered or commented upon. As far as feedback goes, a couple of people responding to issues in the bug report, did cc me a copy of the email they submitted. Most people responding to issues in the bug report, did not cc me anything. So, I might recieve an email which seemed to be related to what I had asked, didn't answer my questions. Thinking that my part of the questions had been solved and this being something more involved, I would look at the bug report to find that usually no, what I had asked still hadn't been answered, but someone elses related problem with this same bug had been answered or commented upon. For instance, someone had suggested running whatever troublesome program with LD_DEBUG=all in the environment. Fine, I did that with an apt-get upgrade. This produced a 36 MB file. I mentioned how big the file was, and where the error message was in that file. Nobody said anything about this file after that. I still have this file. I gather it is of no use, and that I can delete it. I am not necessarily in a hurry to upgrade to a 2.6 kernel. If there are things I can do here, to help get rid of this bug, I am probably willing to try. No, I have no experience at debugging things like libc. I do have more than 25 years experience at programming, mostly number crunching. But unless someone suggests an action plan, I am not going to try and find/solve this thing on my own. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
