[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
gdb redirection arguments are passed as arguments to debugged executable
From: |
Dave Curtis |
Subject: |
gdb redirection arguments are passed as arguments to debugged executable under Cygwin |
Date: |
Sun, 3 Dec 2006 16:09:09 +0000 |
User-agent: |
Internet Messaging Program (IMP) 3.2.5 |
Hi.
I just installed Cygwin and ddd v 3.3.
I am trying to debug an executable called hapclust.exe. The arguments should be
hphc0104.par hcsnp04.dat hphc0104.out. I press F2 and enter these as arguments.
They are displayed as Arguments in the Run Program window as:
hphc0104.par hcsnp04.dat hphc0104.out
If I run the program with a breakpoint near the start it shows:
(gdb) run hphc0104.par hcsnp04.dat hphc0104.out
But, it says argc=0. And nothing appears in the Exectuion Window as it should.
If I print the contents of argv[] I get the following:
argv[0]="/home/dcurtis/hapclust/hapclust"
argv[1]="<"
argv[2]="/dev/tty2"
argv[3]=">"
argv[4]="/dev/tty2"
argv[5]="2>&1"
argv[6]="hphc0104.par" etc
So the arguments which should go to gdb to redirect output are going to my
executable instead.
I can't understand why this is happening to me and why nobody else has reported
it.
Please let me know where to go from here.
Regards
- Dave Curtis
--
Dave Curtis
Dept Adult Psychiatry
Royal London Hospital
Whitechapel, London E1 1BB, UK
Tel: +44-20-7377-7729
Fax: +44-20-7377-7316
www.mds.qmul.ac.uk/statgen/dcurtis.html
log
Description: Binary data
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- gdb redirection arguments are passed as arguments to debugged executable under Cygwin,
Dave Curtis <=