Date: Thu, 12 Mar 1998 19:34:06 -0800 (PST)
Message-Id: <199803130334.TAA08585@adit.ap.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: root AT flying-brick DOT caverock DOT net DOT nz, djgpp AT delorie DOT com
From: Nate Eldredge <eldredge AT ap DOT net>
Subject: Re: I'm stumped! hexdump is dumping...
Precedence: bulk

At 09:29  3/12/1998 NZT-12DST, Eric Gillespie wrote:

>... in this case, hexdump is the file I want to debug. Unfortunately when I 
>tried specifying the args to the program in gdb, it  thought I meant:
>hexdump cat filedir.c | hexdump -t, and pouted at me (telling me quite 
>correctly it couldn't open the file -t  - at least I had THAT right 8-))
>The program works correctly (or appears to) when I fed it a file on the 
>commandline, such as:
>brick:$ hexdump -t filedir.c
>but I have tried to also design with piping in mind...though DOS'es pipes 
>are brain-dead files on disk until finished with...

Yeah, AFAIK you can't use pipes or redirection when debugging. Somebody
please correct me if I'm wrong. I think you'll just have to use your
file-feeding version, and hope you don't have a bug that only shows up when
reading from `stdin'...

Nate Eldredge
eldredge AT ap DOT net