when I am trying to debug the pset3 binary search, I want to use generate to have large numbers to test because my program works fine when I manually enter the values, but only for large values (i.e.10000) it sometimes does not find the value when it is indeed there however, I have searched how to use a standard input when running the program in gdb but it just does not work so first I use this approach pset3 find - gdb with generate as pipe ./generate 10000 0 .

gdb pipe dating-51

I can do things, execute commands, etc..not have a persistent vim session (open until a user quits) and open multiple files...

As for gdb, it's more of a debugging utility that can figure out various information for a user, than give them an entry point to be debugging, more project specific (i.e.

routine projects with routine behavior where this script would be useful).

I basically want to run a batch of commands in either that are very routine, so it can be done for me. vi: I assure you I have a valid reason, however shouldn't the fact that I want to be reason enough ?

Obviously vim would need to always stay open so I can start editing, but gdb doesn't always have to, sometimes i just want to use it to get information, than dump it to stdout. I'm more so curious now that the thought popped into my head.

I'm wondering if vim can be opened and manipulated as if a user were doing it.

I tried setting up a file for vim and I had success, but not the behavior I expected.

If you don't include a breakpoint the gdb will just execute the whole code, without stopping to show you step by step what it's doing.

You may have edited your comment by I will leave mine as a reminder.