corrupted real-time input stream

[Bret Stern]

> -----Original Message-----
> From: Carl Reynolds 
> [mailto:redhat-install-list at hyperbole-software.com] 
> Sent: Tuesday, March 13, 2007 8:31 PM
> To: bret_stern at machinemanagement.com; Getting started with 
> Red Hat Linux
> Subject: Re: corrupted real-time input stream
> 
> Bret Stern wrote:
> >  
> > 
> > 
> >>-----Original Message-----
> >>  <snip...>
> >>
> >>When the server reads the data from the buffer file, it is 
> asking for 
> >>128K bytes. It gets 128K, but the end of the input from 
> about 85K is 
> >>filled with 0s. If I save the buffer file to another 
> location and 'od'
> >>the file, I can see that the data being written to the 
> buffer file is 
> >>correct and does not contain the area of 0s returned by the read.
> >> <snip...>
> >>
> > It sounds like the buffer may be initialized with '0', with the 
> > exception of the note you make regarding the different file 
> location.
> > 
> > Perhaps the buffer already exists (hidden)?? When running your 
> > program, do you check if the buffer already exists?
> > 
> > Debugging is about as much fun as one person can have!
> > 
> > 
> > 
> 
> Bret thanks for your response, I had ensured that the file 
> buffer doesn't exist before running the program. I don't 
> think that is the problem.
> 
> "Debugging is about as much fun as one person can have!" (legally)
> 
> 
> 
> Carl.
> 
> 
> 

Carl,

I don't know the language you're using, but if it was C (for example)
i would set a breakpoint and step through the code. If you set
a watch on the buffer, do that. If not, add a temporary
print function, that prints the buffer data to a text file
so you can see what happens as the program progresses.

Also, many times, it's best to walk-away, then come back with
a clear mind. I've spent huge amounts of time tracking
program bugs, it's actually time well spent.

Regards,