| 00:54.21 | *** join/#edev djerome (~djerome@ip68-98-228-41.ph.ph.cox.net) |
| 01:40.33 | *** join/#edev landley (~landley@70.114.134.56) |
| 02:47.02 | *** join/#edev yuzzi (~yuzzi@bzq-79-181-181-206.red.bezeqint.net) |
| 02:47.04 | yuzzi | how come laptops and handhelds grow gradually slower as they get more beat up? Intuition say they should either work perfectly fine or stop working altogether. |
| 03:03.37 | landley | yuzzi: retry? |
| 04:07.26 | *** join/#edev bzb_ (~bzb@192-0-226-240.cpe.teksavvy.com) |
| 04:33.32 | *** join/#edev [7] (~quassel@rockbox/developer/TheSeven) |
| 05:20.27 | *** join/#edev nullpupp1 (~dustin@freematrix/staff/nullpuppy) |
| 05:31.41 | *** join/#edev bzb (~bzb@192-0-226-240.cpe.teksavvy.com) |
| 06:43.54 | *** join/#edev kuldeepdhaka (~kuldeepdh@117.254.221.37) |
| 07:14.52 | *** join/#edev bzb (~bzb@192-0-226-240.cpe.teksavvy.com) |
| 08:50.24 | *** join/#edev Belliash (~belliash@asiotec/constitutive/belliash) |
| 09:35.32 | *** join/#edev kuldeepdhaka (~kuldeepdh@117.254.221.37) |
| 10:35.44 | *** join/#edev bzb (~bzb@192-0-226-240.cpe.teksavvy.com) |
| 12:09.02 | *** join/#edev g1powermac (~g1powerma@unaffiliated/g1powermac) |
| 12:26.31 | *** join/#edev espiral (maze@unaffiliated/espiral) |
| 12:30.50 | *** join/#edev florian (~fuchs@Maemo/community/contributor/florian) |
| 13:16.53 | *** join/#edev florian (~fuchs@Maemo/community/contributor/florian) |
| 13:20.33 | *** join/#edev bzb (~bzb@192-0-226-240.cpe.teksavvy.com) |
| 13:32.23 | *** join/#edev kuldeepdhaka (~kuldeepdh@117.254.221.43) |
| 15:36.46 | *** join/#edev Belliash (~belliash@asiotec/constitutive/belliash) |
| 15:39.24 | *** join/#edev Belliash (~belliash@asiotec/constitutive/belliash) |
| 15:52.48 | *** join/#edev kuldeepdhaka_ (~kuldeepdh@117.254.222.13) |
| 19:11.10 | *** join/#edev SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 19:15.08 | *** join/#edev S_J (S_J@m83-180-173-149.cust.tele2.se) |
| 19:15.18 | S_J | how do you keep track of how much stack you use? |
| 19:15.57 | S_J | and how much RAM? i mean if you literally need to count bytes manually it is pretty impossible to keep track off when your program is big |
| 19:37.50 | SpeedEvil | There are automated methods. |
| 19:38.09 | SpeedEvil | For example, you can analyse the maximum call depth in your app. |
| 21:01.31 | roxfan | stack painting is a common approach |
| 22:20.51 | *** join/#edev orbarron (~orbarron@nat/ti/x-mxbtvduttjmidxgs) |
| 22:54.01 | *** join/#edev landley (~landley@70.114.134.56) |