I searched through both GBD shorts, but couldn't figure out how the pseude-random numbers can be accessed from within, or piped into, the graphical debugger!? If it`s simply not possible, please let me know and disregard the rest.

When I click Debug in find.c, the Command: field starts with pset3/find/find.c. I tried adding < pset3/find/generate.c 1000 50, < pset3/find/numbers.txt and < ./generate 1000 50 and many more combinations into that field, but always receive the error "bash: line 1: pset3/find/generate.c 1000 50 && echo '' || echo 'Please be sure to stop other debuggers before continuing.': No such file or directory".

Please help! I'm close to copy-pasting generate.c into find.c and converting the numeric CLAs into static variables, just to get started at all with actually testing the sorting and searching part of this task.

Thanks for any advice here :-)

1 Answer 1


I don't think anyone has figured that one out. It may not be possible, but I would be happy for someone to prove me wrong.

OTOH, why do you want to work with so much input data in the debugger? Wouldn't you be better off manually entering data as you step through the program, and restricting the data input to only 3 or 4 elements in the list? Inputting 50 elements (let alone 1000) will probably only overcomplicate the debugging process. You might consider running check50 and looking at the data that it uses to do various tests to do your debugging.

If this answers your question, please click on the check mark to accept. Let's keep up on forum maintenance. ;-)

  • New to CS50, but not new to StackExchange ;-) I wanted to debug as closely to the task as possible, and not provide input manually all the time. However, now that the debugger works, finding the bugs is much faster than I thought it would be. Thanks!
    – Cathryne
    Mar 17, 2016 at 15:38

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .