I thought I would ask a question that is decidedly non-political, although I will admit that a frenchman made my fourth. As well as infinite cheeseburgers, and, of course, jenny.
When I believe to be issuing commands to dos that will step me through gdb, I receive counter-communication that talks of target exec.
What do I need to do to not read of "target exec" and step through?
Dankenstein, -- Nevertheless, it is even harder for the average ape to believe that he has descended from man. H. L. Mencken
I hang with gdb( foo) >text42.txt . Frenchman must be at fualt. -- Wealth - any income that is at least one hundred dollars more a year than the income of one's wife's sister's husband. H. L. Mencken
> On 6 Jul 2008 at 6:16, Ron Ford wrote: >> When I believe to be issuing commands to dos that will step me through gdb, >> I receive counter-communication that talks of target exec.
> What exactly does the error message say?
>> What do I need to do to not read of "target exec" and step through?
> What are you doing at the moment? Try something like
> gdb ./myprog > [snip guff] > (gdb) b main > Breakpoint 1 at [wherever] > (gdb) r
> Then use step/next/etc.
Thanks for the tips, Anton. I was doing a lot of things wrong simultaneously. I can step through it now, but the only information it tells me is what line I'm on and that I'm in fmain.c . The source is in fortran, and I misposted to clc.
Since gdb is bigger than just one syntax, is there an ng where they talk about it more thoroughly? -- All men are frauds. The only difference between them is that some admit it. I myself deny it. H. L. Mencken
> Thanks for the tips, Anton. I was doing a lot of things wrong > simultaneously. I can step through it now, but the only information it > tells me is what line I'm on and that I'm in fmain.c . The source is in > fortran, and I misposted to clc.
It may be that you haven't included debugging symbols in your executable - try investigating compilation options (e.g. -g).
> Since gdb is bigger than just one syntax, is there an ng where they talk > about it more thoroughly?
I'd recommend here if you're debugging C code, or comp.lang.fortran if you're debugging Fortran.
