Erlang Mailing Lists
Author Message

<  Yaws mailing list  ~  How to get the yaws debug info?
start2046
Posted: Sat Nov 07, 2009 4:35 pm Reply with quote
User Joined: 28 Oct 2009 Posts: 19
Hi all,
I'm trying some web frameworks, Erlyweb, Erlang-web and Nitrogen till
now. Do jobs like this are usually not in smooth waters, and then debug
is necessary. But this time, I found couldn't get the yaws' debug info.

I've tried run yaws by --debug flag, and even modify the yaws.app file(
set the debug env variable), both did not work. Sad . The log files in
/var/log/yaws are still *.access/auth.log/report.log/trace.http, no
other debug output file. I check the content of these files, it looks
like there are no debug info in them. So my question is: how can I get
the yaws' debug output? Did I missed something?

As a newbie in web development, I'm curious how to debug yaws itself,
would you mind tell me something about that? Also, any other suggestions
will be appreciated. Thanks in advance.

Eric




Post received from mailinglist
Back to top View user's profile Send private message Send e-mail
Guest
Posted: Sat Nov 07, 2009 9:13 pm Reply with quote
Guest
On Sat, Nov 7, 2009 at 11:34 AM, Eric Liang <eric.l.2046@gmail.com (eric.l.2046@gmail.com)> wrote:
Quote:
Hi all,
I'm trying some web frameworks, Erlyweb, Erlang-web and Nitrogen till
now.
Back to top
start2046
Posted: Sun Nov 08, 2009 4:23 am Reply with quote
User Joined: 28 Oct 2009 Posts: 19
Steve Vinoski wrote:
Quote:


On Sat, Nov 7, 2009 at 11:34 AM, Eric Liang <eric.l.2046@gmail.com (eric.l.2046@gmail.com)> wrote:
Quote:
Hi all,
I'm trying some web frameworks, Erlyweb, Erlang-web and Nitrogen till
now.  Do jobs like this are usually not in smooth waters, and then debug
is necessary. But this time, I found couldn't get the yaws' debug info.

I've tried run yaws by --debug flag, and even modify the yaws.app file(
set the debug env variable), both did not work. Sad .  The log files in
/var/log/yaws are still *.access/auth.log/report.log/trace.http, no
other debug output file. I check the content of these files, it looks
like there are no debug info in them. So my question is: how can I get
the yaws' debug output? Did I missed something?


How about


yaws --interactive --tracetraf --traceout --tracehttp --debug


This runs yaws interactively and shows all kinds of debug and trace info right on stdout.

Thanks Steve.

Actually, I have tried this command,  the debug output is only some PROGRESS REPORTs, but I need more about the program.  The specific case is:
some of my yaws configurations do not work, so I decide to get in yaws to see what happened. The source of yaws looks like use a macro ?Debug which call the functions yaws_debug:assert ->yaws_debug:fail ->io:format, so I guess it will print these information to some place like stdout. but I can't get them from file( no log) or interactive output( the command you suggested ) ? 

Quote:
 
Quote:
As a newbie in web development, I'm curious how to debug yaws itself,
would you mind tell me something about that? Also, any other suggestions
will be appreciated. Thanks in advance.


Why do you feel you need to debug yaws? Are you seeing problems with it? I assume you want to debug your own code running under yaws, not yaws itself.

So as I mentioned before, I guess maybe there is another way to turn on the ?Debug output, which I need to learn about, or the --debug flag does not work.

Quote:


For the ultimate in debugging, learn about the Erlang dbg module. If you have Francesco's and Simon's "Erlang Programming" O'Reilly book <http://oreilly.com/catalog/9780596518189>, read chapter 17 thoroughly, and then read it again. (If you don't have the book, get it.) Try every example and do every exercise at the end of the chapter. I've never run a debugger on any Erlang code I've written, ever, because with the dbg module and tracing, I've never needed a traditional debugger.


--steve

Thanks your recommendation of the book, I've read Joe Armstrong's "Programming Erlang",  some body reminded me of this book, I thought do some practices is more important than just read another book for me. However, maybe this book is readable, I will try to get one later.

Thanks in advance for any more suggestions.

Eric
Post received from mailinglist
Back to top View user's profile Send private message Send e-mail
Guest
Posted: Sun Nov 08, 2009 5:33 am Reply with quote
Guest
On Sat, Nov 7, 2009 at 11:21 PM, Eric Liang <eric.l.2046@gmail.com (eric.l.2046@gmail.com)> wrote:
Quote:
Steve Vinoski wrote:
Quote:


On Sat, Nov 7, 2009 at 11:34 AM, Eric Liang <eric.l.2046@gmail.com (eric.l.2046@gmail.com)> wrote:
Quote:
Hi all,
I'm trying some web frameworks, Erlyweb, Erlang-web and Nitrogen till
now.
Back to top
start2046
Posted: Sun Nov 08, 2009 6:32 am Reply with quote
User Joined: 28 Oct 2009 Posts: 19
Steve Vinoski wrote:
Quote:


On Sat, Nov 7, 2009 at 11:21 PM, Eric Liang <eric.l.2046@gmail.com (eric.l.2046@gmail.com)> wrote:
Quote:
Steve Vinoski wrote:
Quote:


On Sat, Nov 7, 2009 at 11:34 AM, Eric Liang <eric.l.2046@gmail.com (eric.l.2046@gmail.com)> wrote:
Quote:
Hi all,
I'm trying some web frameworks, Erlyweb, Erlang-web and Nitrogen till
now.  Do jobs like this are usually not in smooth waters, and then debug
is necessary. But this time, I found couldn't get the yaws' debug info.

I've tried run yaws by --debug flag, and even modify the yaws.app file(
set the debug env variable), both did not work. Sad .  The log files in
/var/log/yaws are still *.access/auth.log/report.log/trace.http, no
other debug output file. I check the content of these files, it looks
like there are no debug info in them. So my question is: how can I get
the yaws' debug output? Did I missed something?


How about


yaws --interactive --tracetraf --traceout --tracehttp --debug


This runs yaws interactively and shows all kinds of debug and trace info right on stdout.


Thanks Steve.

Actually, I have tried this command,  the debug output is only some PROGRESS REPORTs, but I need more about the program.  The specific case is:
some of my yaws configurations do not work, so I decide to get in yaws to see what happened. The source of yaws looks like use a macro ?Debug which call the functions yaws_debug:assert ->yaws_debug:fail ->io:format, so I guess it will print these information to some place like stdout. but I can't get them from file( no log) or interactive output( the command you suggested ) ? 



Those macros have to be compiled in. Build your code like this:


make TYPE=debug


Install the result and run with the command line I gave you above.


If you keep having problems, don't hesitate to ask for help with your code on this list.


--steve

Thanks a lot. This is exactly what I want.  Smile

Eric

Post received from mailinglist
Back to top View user's profile Send private message Send e-mail
wuji
Posted: Fri Sep 14, 2012 7:14 am Reply with quote
User Joined: 10 Aug 2012 Posts: 654
in the suicides.The doctor's mantra was "dying is not a crime," and and imitation designer *beep* and he made national headlines with his invention -- the thanatron, Greek
suicide machine -- which gave patients a "dignified, humane and painless" death."The death."The cheap polo shirts death."The people we were helping, there was never any question in their
said Nicol. "None of the patients ever had a wavering moment in in cheap designer *beep* in their decision."A pull of the trigger released a drug to induce
deep coma. Once asleep, a timer would inject a lethal dose of of buy real jordans of potassium chloride to stop the heart.Later, he used a "mercitron," or
machine, after his medical license was revoked after the first two deaths deaths buy real jordans deaths and he could no longer get the substances required for the
were those in the movement who didn't agree with his methodology," Nicol Nicol cheap replica *beep* Nicol said. "He was thwarted in that goal at every turn, but
Back to top View user's profile Send private message

Display posts from previous:  

All times are GMT
View next topic
View previous topic
Page 1 of 1
Erlang Forum - Trap Exit Forum Index  ~  Yaws mailing list
This forum is locked: you cannot post, reply to, or edit topics.

Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum
Hosted by Erlang Solutions    |    Powered by phpBB and NoseBleed v1.14