Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

Accept cookies Cookie settings

Cookie settings

We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.

Basic
Functional

Normal
Functional + analytics

Complete
Functional + analytics + social media + embedded videos

Accept cookies

undo.io
Documentation
Support

- - Knowledge base
Product Ideas
Product Updates
Events
Groups

Create topic
Login

👋🏾👋👋🏼 Welcome to the Undo Community

Community Categories

News & Updates

8 topics
0 Replies

Ask the community

13 topics
14 Replies

General bug hunting

6 topics
5 Replies

Featured Topics

News

Changelog: 6.6 Manchego release coming soon

Forum|Forum|1 month ago

370

Release

Time Travel Debug for VS Code Out Now

3 months ago

691

Recently active
Help others

Recently active

How does a undolr_stop() or undolr_discard() failure affect the state of the debugged program?

If, while recording through the API, one of the undolr_stop() or undolr_discard() functions fails (e.g. returns -1), what does that imply for the debugged program?What measures should a programmer take when such failures are met?

Got a Question?

How would you debug a silent EINTR /without/ software failure replay?

I was asked to take a look at a failure of a test that I wrote many years ago. This failure was, as far as we could tell, new, but it didn’t look like a regression. The test was multi-threaded with asynchronous signals using setitimer() to fire SIGALRMs at it. It appeared to have completed successfu...

How would you tackle...?

`Ugo event` seemingly going to the wrong event

Recently while investigating an issue for a customer I noticed the following: (udb) ugo event prev name=='write'going to: ref=0x1fc054f4c170 in_code=0 time_bbcount=223466223298 time_extra=18446744073709551615 code=write size=80 result=70x00007f4fc89e0c0b in write () from /tmp/undodb.8444.1617966303....

Got a Question?

Debugging the wetware component of the protocol stack

As an example of how the Slack integration looks, how would anybody go about unblocking the wetware pipe to allow thoughts and conversations to flow into the system?

How would you tackle...?

Build better products

Feedback or suggestions for our product? Submit and vote on product ideas.

View ideas

Sign up

Already have an account? Login

Username *

E-mail address *

Company

Password *

I accept the terms & conditions

loginBox.register.email_repeat

Login to the community

No account yet? Create an account

Username or Email

Password

Remember me

Forgot password?

Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.

Username or e-mail

Back to overview

Scanning file for viruses.

Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.

This file cannot be downloaded

Sorry, our virus scanner detected that this file isn't safe to download.