On Wed, 18 Feb 2004, Ross Boulet wrote:
> > On Wed, 18 Feb 2004, Ross Boulet wrote:
> >
> > > > On Wed, 18 Feb 2004, Ross Boulet wrote:
> > > >
>
> [...snip...]
>
> > Ok, time for "Pipes 101". A pipe is essentially a bounded (character)
> > buffer. The producer application fills the buffer (by w
> On Wed, 18 Feb 2004, Ross Boulet wrote:
>
> > > On Wed, 18 Feb 2004, Ross Boulet wrote:
> > >
[...snip...]
>
> Ok, time for "Pipes 101". A pipe is essentially a bounded (character)
> buffer. The producer application fills the buffer (by writing to the
> pipe), and the consumer application e
On Wed, 18 Feb 2004, Ross Boulet wrote:
> > On Wed, 18 Feb 2004, Ross Boulet wrote:
> >
> [...snip...]
> > > Just adding my 2 cents and hopefully to learn something:
> > >
> > > I know how to use pipes but I don't know how they are handled "under
> > > the covers". Wouldn't piping the strace to t
> On Wed, 18 Feb 2004, Ross Boulet wrote:
>
[...snip...]
> > Just adding my 2 cents and hopefully to learn something:
> >
> > I know how to use pipes but I don't know how they are
> handled "under the
> > covers". Wouldn't piping the strace to tail or grep still produce a
> > temporary file of a
On Wed, 18 Feb 2004, Ross Boulet wrote:
> > On Mon, 16 Feb 2004, Thomas L Roche wrote:
> >
> > > Is there a way to limit the size of the strace output _file_, rather
> > > than just the output file buffer, while preserving desired
> > > information?
> > >
> > > I previously used strace to debug th
>
> On Mon, 16 Feb 2004, Thomas L Roche wrote:
>
> > Is there a way to limit the size of the strace output _file_, rather
> > than just the output file buffer, while preserving desired
> > information?
> >
> > I previously used strace to debug the problem that 20040213
> induced in
> > emacs 'de
On Tue, Feb 17, 2004 at 12:33:34PM -0500, Christopher Faylor wrote:
> On Tue, Feb 17, 2004 at 11:09:39AM -0500, Christopher Faylor wrote:
> >>I believe a destructor would be cleaner, and the current code obviously
> >>misses at least one more place where this is needed. Unfortunately, with
> >>my
On Mon, Feb 16, 2004 at 12:36:14PM -0500, Thomas L Roche wrote:
>
> My experience using and contributing to OSS has created expectations
> that
>
> * projects advance faster when their leaders encourage assistance from
> the community and bootstrap members' attempts to assist better (e.g.
> P
On Tue, Feb 17, 2004 at 12:14:58AM -0500, Thomas L Roche wrote:
>Larry Hall Mon, 16 Feb 2004 16:42:48 -0500
>> In your case, it sounds to me like you could just pipe the output of
>> strace into grep looking for a keyword or two specific to the error
>
>Unfortunately no: the phrase 'commit memory f
On Tue, Feb 17, 2004 at 11:09:39AM -0500, Christopher Faylor wrote:
>>I believe a destructor would be cleaner, and the current code obviously
>>misses at least one more place where this is needed. Unfortunately, with
>>my copyright assignment in flux, I can't send in a patch. If noone fixes
>>thi
On Mon, Feb 16, 2004 at 10:09:07PM -0500, Igor Pechtchanski wrote:
>On Mon, 16 Feb 2004, Pierre A. Humblet wrote:
>
>> At 01:20 PM 2/16/2004 -0500, Christopher Faylor wrote:
>> >On Mon, Feb 16, 2004 at 12:36:14PM -0500, Thomas L Roche wrote:
>> >>
>> >>No, I have discovered considerably more. Conse
summary:
strace on 20040216 failed to emit 'commit memory for cygwin heap'
despite unzip failing in the recent way: tail of output (from point
of failure) at end of post.
details:
Christopher Faylor Mon, 16 Feb 2004 13:20:31 -0500
>> If you look at the changes that I made to cygwin yesterday:
>
On Mon, 16 Feb 2004, Pierre A. Humblet wrote:
> At 10:09 PM 2/16/2004 -0500, Igor Pechtchanski wrote:
> >On Mon, 16 Feb 2004, Pierre A. Humblet wrote:
> >
> >> At 01:20 PM 2/16/2004 -0500, Christopher Faylor wrote:
> >> >On Mon, Feb 16, 2004 at 12:36:14PM -0500, Thomas L Roche wrote:
> >> >>
> >>
At 10:09 PM 2/16/2004 -0500, Igor Pechtchanski wrote:
>On Mon, 16 Feb 2004, Pierre A. Humblet wrote:
>
>> At 01:20 PM 2/16/2004 -0500, Christopher Faylor wrote:
>> >On Mon, Feb 16, 2004 at 12:36:14PM -0500, Thomas L Roche wrote:
>> >>
>> >>No, I have discovered considerably more. Consequently my qu
On Mon, 16 Feb 2004, Pierre A. Humblet wrote:
> At 01:20 PM 2/16/2004 -0500, Christopher Faylor wrote:
> >On Mon, Feb 16, 2004 at 12:36:14PM -0500, Thomas L Roche wrote:
> >>
> >>No, I have discovered considerably more. Consequently my question is,
> >>is the path_conv bad?
> >
> >What you are deb
At 01:20 PM 2/16/2004 -0500, Christopher Faylor wrote:
>On Mon, Feb 16, 2004 at 12:36:14PM -0500, Thomas L Roche wrote:
>>
>>No, I have discovered considerably more. Consequently my question is,
>>is the path_conv bad?
>
>What you are debugging is the consequences of cmalloc being NULL. While
>tha
On Mon, 16 Feb 2004, Thomas L Roche wrote:
> Is there a way to limit the size of the strace output _file_, rather
> than just the output file buffer, while preserving desired
> information?
>
> I previously used strace to debug the problem that 20040213 induced in
> emacs 'desktop', therefore in e
Is there a way to limit the size of the strace output _file_, rather
than just the output file buffer, while preserving desired
information?
I previously used strace to debug the problem that 20040213 induced in
emacs 'desktop', therefore in emacs' startup; nevertheless the
resulting strace.out wa
On Mon, Feb 16, 2004 at 12:36:14PM -0500, Thomas L Roche wrote:
>Christopher Faylor Mon, 16 Feb 2004 09:49:19 -0500
>> What you have discovered is that when memcpy is given a NULL pointer
>> it will [cause] a SEGV.
>
>No, I have discovered considerably more. Consequently my question is,
>is the pat
Ken Thompson Mon, 16 Feb 2004 08:15:11 -0500
>> We continually get new subscribers who somehow have the expectation
>> that somehow CGF is responsible for fixing all problems.
My experience using and contributing to OSS has created expectations
that
* projects advance faster when their leaders en
summary:
unzip has been abending when run with recent cygwin1.dll: a gdb trace
(showing overflow?) and configuration information is included. I would
appreciate assistance locating the failing code(s) and the
maintainer(s) to contact.
details:
I would appreciate any assistance anyone could provi
21 matches
Mail list logo
