Newest at the top
2025-07-21 20:19:22 +0200 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) |
2025-07-21 20:18:15 +0200 | r-sta | (~r-sta@cpc142694-benw13-2-0-cust901.16-2.cable.virginm.net) (Quit: Client closed) |
2025-07-21 20:18:11 +0200 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Read error: Connection reset by peer) |
2025-07-21 20:16:39 +0200 | <r-sta> | this is utterly hopeless, i give up |
2025-07-21 20:16:15 +0200 | <myfirstname> | I haven't used it much, and don't remember precisely how things work. I do remember getting it to work tho, just takes a bit of getting used to. |
2025-07-21 20:16:06 +0200 | <r-sta> | ... [<unknown>] ghci> |
2025-07-21 20:16:05 +0200 | <r-sta> | _exception :: e = _ |
2025-07-21 20:16:05 +0200 | <r-sta> | Stopped in <exception thrown>, <unknown> |
2025-07-21 20:16:04 +0200 | <r-sta> | ... [<unknown>] ghci> :continue |
2025-07-21 20:16:03 +0200 | <r-sta> | and then :continue gives; |
2025-07-21 20:15:51 +0200 | <r-sta> | _exception :: e = _ |
2025-07-21 20:15:51 +0200 | <r-sta> | Stopped in <exception thrown>, <unknown> |
2025-07-21 20:15:50 +0200 | <r-sta> | ... [<unknown>] ghci> main |
2025-07-21 20:15:26 +0200 | <r-sta> | it just says; |
2025-07-21 20:15:21 +0200 | <r-sta> | hmm, if i do :break main |
2025-07-21 20:13:30 +0200 | <r-sta> | until i see something looping? |
2025-07-21 20:13:22 +0200 | <r-sta> | ok, so i just put like :break 2, and then :continue |
2025-07-21 20:13:09 +0200 | <r-sta> | ditto |
2025-07-21 20:12:53 +0200 | <myfirstname> | unhelpful >_> |
2025-07-21 20:12:47 +0200 | <myfirstname> | The <<loop>> error is very frustrating and helpful though. would love a better method of handling it |
2025-07-21 20:12:10 +0200 | <r-sta> | the above code i cant see how it could have an error, so i guess it must be somewhere else |
2025-07-21 20:12:05 +0200 | <myfirstname> | https://downloads.haskell.org/~ghc/7.4.1/docs/html/users_guide/ghci-debugger.html |
2025-07-21 20:11:49 +0200 | <r-sta> | myfirstname: how is this done? |
2025-07-21 20:11:48 +0200 | <myfirstname> | know of* |
2025-07-21 20:11:34 +0200 | <r-sta> | https://paste.tomsmeding.com/3NOfOw98 |
2025-07-21 20:11:34 +0200 | <r-sta> | the reason for asking is because the error appeared after i added this; |
2025-07-21 20:11:34 +0200 | <myfirstname> | All I know if is using ghci's debugger and stepping thru it |
2025-07-21 20:10:50 +0200 | <r-sta> | like, how far down an infine list would it evaluate before determining it was looping? |
2025-07-21 20:10:17 +0200 | <r-sta> | also, is there any way that a function can "seem" to loop, but actually not |
2025-07-21 20:10:08 +0200 | jmcantrell | (~weechat@user/jmcantrell) jmcantrell |
2025-07-21 20:09:29 +0200 | falafel | (~falafel@2a0c:5a87:3104:8f01::f709) (Remote host closed the connection) |
2025-07-21 20:05:22 +0200 | <r-sta> | im looking for methods to step through subsequent function calls, so i can see the name of the function that is entering into a loop |
2025-07-21 20:04:58 +0200 | <r-sta> | but there must be some value dependant branching that i cant locate |
2025-07-21 20:04:45 +0200 | <r-sta> | i cannot understand how this causes it to go down a looping branch of code |
2025-07-21 20:04:31 +0200 | <r-sta> | but it only occurs under some certain parametrizations |
2025-07-21 20:04:18 +0200 | <r-sta> | i have turned off random number random entropy source so that the error is reproducable |
2025-07-21 20:03:56 +0200 | <r-sta> | it is part of a machine learning experiment which retrains a parametric opperator by stochastic methods |
2025-07-21 20:03:49 +0200 | AlexNoo | (~AlexNoo@5.139.233.5) (Ping timeout: 260 seconds) |
2025-07-21 20:03:22 +0200 | caubert | (~caubert@user/caubert) caubert |
2025-07-21 20:03:10 +0200 | <r-sta> | hi, im wondering about how to do stack traces for profiling a <<loop>> error that im stuck trying to find in a large illegible piece of code |
2025-07-21 20:02:42 +0200 | r-sta | (~r-sta@cpc142694-benw13-2-0-cust901.16-2.cable.virginm.net) |
2025-07-21 20:01:58 +0200 | AlexZenon | (~alzenon@5.139.233.5) (Ping timeout: 240 seconds) |
2025-07-21 20:00:44 +0200 | caubert | (~caubert@user/caubert) (Ping timeout: 260 seconds) |
2025-07-21 19:52:48 +0200 | ciadsyyyl^ | (~ciadsyyyl@99-73-20-238.lightspeed.tukrga.sbcglobal.net) (Ping timeout: 252 seconds) |
2025-07-21 19:52:36 +0200 | Tuplanolla | (~Tuplanoll@91-159-69-59.elisa-laajakaista.fi) Tuplanolla |
2025-07-21 19:52:12 +0200 | uncletim13[m] | (~uncletim1@static.102.80.201.138.clients.your-server.de) |
2025-07-21 19:51:58 +0200 | Tuplanolla | (~Tuplanoll@91-159-69-59.elisa-laajakaista.fi) (Ping timeout: 240 seconds) |
2025-07-21 19:51:58 +0200 | uncletim13[m] | (~uncletim1@static.102.80.201.138.clients.your-server.de) (Ping timeout: 240 seconds) |
2025-07-21 19:50:53 +0200 | Square2 | (~Square@user/square) Square |
2025-07-21 19:50:29 +0200 | tzh | (~tzh@c-76-115-131-146.hsd1.or.comcast.net) (Read error: Connection reset by peer) |