On 10/06/2013 01:13 PM, Michael Stone wrote:
> On Sun, Oct 06, 2013 at 11:33:17AM -0700, Octavio Alvarez wrote:
> You seem to be creating overcomplicated possibilities. If we were to
> create a -dbg package, here's what would be different:
Only in my particular case, which inolves timeout and time
On Sun, Oct 06, 2013 at 11:33:17AM -0700, Octavio Alvarez wrote:
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 valg
-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 co
Octavio Alvarez wrote:
> Bob Proulx wrote:
> > Which coreutils bug are we talking about here?
>
> The one that I found to be in eglibc (and not coreutils' timeout): the
> 8-byte memory leak. This is not the same I mentioned earlier, but also
> discovered via timeout.
Just to be clear then I take
On Sat, Oct 05, 2013 at 07:15:33PM -0700, Octavio Alvarez wrote:
Reporting the bug has turned pointless now; you know what happens:
incomplete debugging information makes it more difficult for upstream.
That's why if I report a bug without a full backtrace, chances of the
bug being disregarded as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/05/2013 10:51 PM, Bob Proulx wrote:
> Octavio Alvarez wrote:
>> Reporting the bug has turned pointless now; you know what
>> happens: incomplete debugging information makes it more difficult
>> for upstream. That's why if I report a bug without a
Octavio Alvarez wrote:
> Reporting the bug has turned pointless now; you know what happens:
> incomplete debugging information makes it more difficult for upstream.
> That's why if I report a bug without a full backtrace, chances of the
> bug being disregarded as NEEDINFO raise significantly. And u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/05/2013 05:54 PM, Bob Proulx wrote:
> Hmm... Regarding valgrind... The coreutils gets run through
> valgrind routinely. There are always lots of false positives.
Well... in this case the 8-byte unfreed region is not. The bug
apparently lies
package: coreutils
severity: wishlist
Some issues require debugging of certain coreutils tools (e.g. chroot
in bug #649146). For those cases, it would be very useful to have a
coreutils-dbg package. As an aside, redhat does provide this as a
convenience to their developers.
Thanks,
Mike
--
9 matches
Mail list logo
