aboutsummaryrefslogtreecommitdiffstats
path: root/railties/doc/guides/source
diff options
context:
space:
mode:
authorHongli Lai (Phusion) <hongli@phusion.nl>2008-11-04 16:05:47 +0100
committerHongli Lai (Phusion) <hongli@phusion.nl>2008-11-04 16:05:47 +0100
commitbc0bc83b90316aa1b4ba157d9d6f88f1fab50883 (patch)
treec86d7691ae1d55c1735309f3816f31e5bebbb4f5 /railties/doc/guides/source
parentf22458ef85eb2d7bdf25943395baf9335e0805ce (diff)
downloadrails-bc0bc83b90316aa1b4ba157d9d6f88f1fab50883.tar.gz
rails-bc0bc83b90316aa1b4ba157d9d6f88f1fab50883.tar.bz2
rails-bc0bc83b90316aa1b4ba157d9d6f88f1fab50883.zip
Remove invalid use of [source, log] in the 'Debugging Rails Applications' guide.
Diffstat (limited to 'railties/doc/guides/source')
-rw-r--r--railties/doc/guides/source/debugging_rails_applications.txt10
1 files changed, 2 insertions, 8 deletions
diff --git a/railties/doc/guides/source/debugging_rails_applications.txt b/railties/doc/guides/source/debugging_rails_applications.txt
index b67f4be126..c61e6bb6e6 100644
--- a/railties/doc/guides/source/debugging_rails_applications.txt
+++ b/railties/doc/guides/source/debugging_rails_applications.txt
@@ -31,7 +31,7 @@ The `debug` helper will return a <pre>-tag that renders the object using the YAM
You'll see something like this:
-[source, log]
+[source, yaml]
----------------------------------------------------------------------------
--- !ruby/object:Post
attributes:
@@ -64,7 +64,7 @@ The `to_yaml` method converts the method to YAML format leaving it more readable
As a result of this, you will have something like this in your view:
-[source, log]
+[source, yaml]
----------------------------------------------------------------------------
--- !ruby/object:Post
attributes:
@@ -94,7 +94,6 @@ Another useful method for displaying object values is `inspect`, especially when
Will be rendered as follows:
-[source, log]
----------------------------------------------------------------------------
[1, 2, 3, 4, 5]
@@ -204,7 +203,6 @@ end
Here's an example of the log generated by this method:
-[source, log]
----------------------------------------------------------------------------
Processing PostsController#create (for 127.0.0.1 at 2008-09-08 11:52:54) [POST]
Session ID: BAh7BzoMY3NyZl9pZCIlMDY5MWU1M2I1ZDRjODBlMzkyMWI1OTg2NWQyNzViZjYiCmZsYXNoSUM6J0FjdGl
@@ -258,7 +256,6 @@ end
If you see the message in the console or logs:
-[source, log]
----------------------------------------------------------------------------
***** Debugger requested, but was not available: Start server with --debugger to enable *****
----------------------------------------------------------------------------
@@ -631,7 +628,6 @@ You can include any number of these configuration lines inside a `.rdebugrc` fil
Here's a good start for an `.rdebugrc`:
-[source, log]
----------------------------------------------------------------------------
set autolist
set forcestep
@@ -671,7 +667,6 @@ RAILS_ENV=production BLEAK_HOUSE=1 ruby-bleak-house ./script/server
Make sure to run a couple hundred requests to get better data samples, then press `CTRL-C`. The server will stop and Bleak House will produce a dumpfile in `/tmp`:
-[source, log]
----------------------------------------------------------------------------
** BleakHouse: working...
** BleakHouse: complete
@@ -680,7 +675,6 @@ Make sure to run a couple hundred requests to get better data samples, then pres
To analyze it, just run the listed command. The top 20 leakiest lines will be listed:
-[source, log]
----------------------------------------------------------------------------
191691 total objects
Final heap size 191691 filled, 220961 free