-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/06/2013 09:24 AM, Bob Proulx wrote: > You were claiming that reports were being rejected due to lack of > a full backtrace. This shocked us. I haven't ever seen such > cases. That isn't how it works. We were asking for examples so > that we could address the problem. That is the next step. Collect > data. And being part of upstream means that we could make amends > for any just grievance. But no examples have been provided. I > think you are thinking of a different upstream group. Therefore > that claim is completely unjustified for coreutils.
Oh! I should have chosen better words. Sorry about that. I was speaking generically, not specifically about coreutils. I have never touched coreutils upstream. I have touched other upstreams, seen bug reports and how the reports just get forgotten because of lack of information. Lack of symbols is a *typical* case. My claim was that it happens so often in so many projects that I just assumed it will happen everywhere. It means that the standard practice of providing full information is not possible with stock Debian and standard Debian practices in this particular situation. Yes, I'm aware that I can download and compile the source myself. I just thought this would not have been necessary, that the lack of coreutils-dbg was just an omission, not deliberate. I did not mean to claim rejection of patches from coreutils; sorry about that. >> But we digress. In breaf, what you are saying is: WONTFIX, is >> this correct? > > So far in this thread we have been discussing the justification for > a dbg package. And so far in the thread as far as I can read there > has not been any justification for it. (Apart from the original > bug submitter.) Without justification for it then I expect it will > likely be that the dbg package won't happen. As the discussion has evolved and I have learned more, my point is now pretty much the same: a bug on eglibc. I was testing an app with "valgrind timeout ./app" so problems that did not belong to my app started appearing on the valgrind report. Fortunately I just did "timeout valgrind ./app" instead. However, this misstep revealed a leak in timer_create() from eglibc, which I wanted to debug. This leak is most probably even affecting your machine. I have never used timer_create(). I currently don't know how to. I will learn as I go. Most probably I will get it wrong the first N times, so debugging with timeout is *by far* easier. It's this simple: instead of "apt-get install coreutils-dbg" I have to recompile coreutils (which may imply installing other packages). Oh, wait, because it is not guaranteed to work in the exact same way (lack of Debian patches). To guarantee it use the Debian package, so now I have to hack it to not strip the symbols. It may be easy, but I don't know how yet. Another thing to learn as I go. Each step that I have to learn as I go has a set of variables, and each variable makes the problem more complex until I the time and work needed is greater than my interest. I was initially willing to debug and attempt a fix but now I'm not sure anymore. Just search for "timer_create() leak" in Google. You'll find a lot of instances where people just suppresses or ignore the error because it lies outside of their skill set. Many many applications now have this leak. In conclusion: your delimitation of "worth it or not" is leaving out at least one long-reaching and important possibility. I spoke about it, that doesn't imply I am the only one facing it. That was my best shot. :) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBAgAGBQJSUaztAAoJEDsli1MUcl7If80P/RkCR5NauOdSdffAroqgp0XH e+EfMDQMiWrV+b0kLqja7Lp2JN/MGh+/qcJZ/fgwcovGsP/k/lOOYjGI0vhp6Z/O quuzeYOCpXu/B/f/g1W/rwBD8YLd+P9lju8fxuxVx8ZbkbQNIo5mAJK0MVOgBL/t yTWy5RERHKwqzNZsDwKljQ1QDL4Ae4XVIZddc3FNbVow7LlMjff0g1I3lXWWl0Q4 urZ7qU3Ltoxtac7rmhI0hIzJ5P8z5V4CKiEaB+78ZkIiv0fdcw1UTc7QkE/rMj+4 vp08DHC/g30PHJd7zq0fEjDKvNr9cYVqBdqx2wI92q0dDp4CWIYcFGYQRocVkKhj Fm/hLfbNPj0Vcywx5MS7PUv2yW8uo3XKVXRkgd5bb3dpzitfvyHQOxpAqfjyrEEp lr7OVPdhqLj2WvzaWrT1S0wvKE7/5R9LFDabUphyQZ36YkIAG0wE7MjJPrqw1Gu9 UQaBOFsBnMnm1HO4Dvpvoaao5T8r4kjqI8nToBOEesCPVvwVALwm9EVM8U0c0458 OVTV8O6WojWEHb05WOh8S+rjqi2oM9gEMDzjGbzrxxYIrclX/oBKCzDSw4CUATHk w2nK84NkLsGwm+rCVw4EDsj6GXo4wkLg+qoH6ErXa0lruMmDGfumLetQiwKKaerg +2CUermSHkdCEO2VL59K =Ukyc -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
