Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Official Revel Debugging Guide #523

Open
brendensoares opened this issue Feb 25, 2014 · 13 comments
Open

Official Revel Debugging Guide #523

brendensoares opened this issue Feb 25, 2014 · 13 comments
Labels
Milestone

Comments

@brendensoares
Copy link
Member

In #95 we discussed the options for using gdb to debug a Revel app.

I'd like to get together an official guide on how to set breakpoints and walkthrough a Revel app at runtime with gdb and hopefully with some IDE integration.

@brendensoares brendensoares added this to the Backlog milestone Feb 25, 2014
@verdverm
Copy link
Contributor

@brendensoares
Copy link
Member Author

How is GoConvey related to runtime debugging? It definitely looks great for unit testing, but I don't see the relation.

Side point: our testing suite is already pretty nice with browser output, but maybe we could enhance it further with some inspiration from GoConvey.

@mihaihuluta
Copy link

Is there an official debugging guide for Revel? Personally I just want to follow clear steps in order to be able to debug a Revel application (currently it matters less if its command line based or IDE based). I really do not want to spend time trying to figure out how to do it. Specially that I am new to both Golang and Revel.

@brendensoares
Copy link
Member Author

@mihaihuluta there is still no official guide to give you easy steps. Sorry.

@cellis
Copy link

cellis commented Jun 8, 2014

I'm also interested in this. Having spent about 5 hours trying to get the sublimetext 3 debugger (gogdb) working for simple go programs, i'm thinking it's not going to be easy with Revel.

I think a gentler tutorial to debugging with gdb is this: http://lincolnloop.com/blog/introduction-go-debugging-gdb/

@mihaihuluta
Copy link

In my case this answer helped a lot: http://stackoverflow.com/questions/23952886/revel-debugging-how-to

@brendensoares
Copy link
Member Author

Thanks for the helpful resources @cellis and @mihaihuluta :]

@brendensoares
Copy link
Member Author

#294

@pedromorgan
Copy link
Member

Do we need to put this in the FAQ ?

@brendensoares
Copy link
Member Author

@pedromorgan we need a guide for it somewhere, eventually. Where were you thinking? The website or the wiki?

@pedromorgan
Copy link
Member

I'd stick it in the manual as a quick quide, with some footer links to some externals..

@brendensoares
Copy link
Member Author

@pedromorgan that sounds like a good idea.

@pedromorgan
Copy link
Member

started a page here..
http://revel-docs.daffodil.uk.com/manual/debug.html

Just need time to check and finish it.. hopefully by the weekend

On 5 January 2015 at 22:18, Brenden Soares notifications@github.com wrote:

@pedromorgan https://github.com/pedromorgan that sounds like a good
idea.


Reply to this email directly or view it on GitHub
#523 (comment).

@brendensoares brendensoares added effort-hours Less than a day priority-should sooner rather than later labels Jun 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants