4 ms·

I tried playing around with this and I can't see it being useful for me currently. If the source and tracing information were more tightly integrated it would b

I tried playing around with this and I can't see it being useful for me currently. If the source and tracing information were more tightly integrated it would be a lot more useful. Offering a more traditional debugging experience with the ability to rewind time to the last time a value is set would also make it valuable. A specific issue I ran into was that multi dimensional arrays do get logged as changing when a value is set in the bottom layer. This meant for my application the were a bunch of init calls setting that value, but none of the actual logical changes were tracked.

HenriNext 7y ago
The source and tracing sides will definitely get fully integrated. This is only the second beta that even has the source side at all, so it's just "early days". The line/statement level traditional debugging is possible to implement with currently captured information, but the implementation is seriously hard, likely in 2021+ timeframe. About the specific issue: I'd really like to get that fixed, do you think you could shoot me an email so that I can followup in case that i cannot repro the bug (my email is in the contact page)? Many thanks for the feedback & apologies that the initial experience wasn't so great
- thethirdone 7y ago
  I made a gist [0] that demonstrates the issue. Line 5 does not make a node in the timeline. I look forward to seeing what bugjail becomes in the future. [0]: https://gist.github.com/TheThirdOne/7af9356dfb89d218162500179514b2c6 https://gist.github.com/TheThirdOne/7af9356dfb89d21816250017...
  - HenriNext 7y ago
    Thanks, appreciated. I get this fixed.
josteink 7y ago
> Offering a more traditional debugging experience with the ability to rewind time to the last time a value is set would also make it valuable. Visual Studio has this. It’s called time-travel debugging, and it makes your code run really slow :)

HenriNext 7y ago

The source and tracing sides will definitely get fully integrated. This is only the second beta that even has the source side at all, so it's just "early days". The line/statement level traditional debugging is possible to implement with currently captured information, but the implementation is seriously hard, likely in 2021+ timeframe. About the specific issue: I'd really like to get that fixed, do you think you could shoot me an email so that I can followup in case that i cannot repro the bug (my email is in the contact page)? Many thanks for the feedback & apologies that the initial experience wasn't so great

thethirdone 7y ago
I made a gist [0] that demonstrates the issue. Line 5 does not make a node in the timeline. I look forward to seeing what bugjail becomes in the future. [0]: https://gist.github.com/TheThirdOne/7af9356dfb89d218162500179514b2c6 https://gist.github.com/TheThirdOne/7af9356dfb89d21816250017...
- HenriNext 7y ago
  Thanks, appreciated. I get this fixed.

josteink 7y ago

> Offering a more traditional debugging experience with the ability to rewind time to the last time a value is set would also make it valuable. Visual Studio has this. It’s called time-travel debugging, and it makes your code run really slow :)