Timeline for gdb piping not working
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 12, 2015 at 8:47 | comment | added | ChrisG | Well the reason you use gdb usually is to find the errors that are produced. If your program doesn't have errors it should run from start to end without a problem. | |
| Aug 12, 2015 at 8:46 | vote | accept | Ingrid Keupers | ||
| Aug 12, 2015 at 8:46 | comment | added | Ingrid Keupers | I know, but it should still run without an error, no? Anyways, luckily it works now, thanks | |
| Aug 12, 2015 at 8:44 | comment | added | ChrisG | 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. | |
| Aug 12, 2015 at 8:42 | comment | added | Ingrid Keupers | I have included in the question: (also tried just run 65516 < testNumbers10000.txt but gave the same error) | |
| Aug 12, 2015 at 8:41 | comment | added | ChrisG |
No you didn't. You typed: run args 65516 < testNumbers10000.txt. If you payed a little closer attention to what you type, what you copy-paste from sites, and what others tell you, you would have figured it out. Since including the string args makes your argc equal to 3, your program exits.
|
|
| Aug 12, 2015 at 8:41 | vote | accept | Ingrid Keupers | ||
| Aug 12, 2015 at 8:41 | |||||
| Aug 12, 2015 at 8:39 | comment | added | Ingrid Keupers | why is there a difference if you put a breakpoint or not? | |
| Aug 12, 2015 at 8:34 | history | answered | ChrisG | CC BY-SA 3.0 |