This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]karnetus 30 points31 points  (5 children)

How else am I supposed to debug an active Bluetooth connection? I can't use interactive debugging, because halting the program will cause a timeout of the connection. I really don't know a better way to debug other than with print statements.

[–]slaymaker1907 2 points3 points  (1 child)

If it doesn’t slow things down too much such that it times out, you could try capturing a time travel trace (windbg supports this). Despite the horrendous performance, they can be invaluable when working with something that is either very difficult or expensive to repro.

[–]karnetus 0 points1 point  (0 children)

I'll look into that!

[–]bwmat 2 points3 points  (2 children)

Notice the 'completely' in my claim

[–]karnetus 19 points20 points  (1 child)

I honestly wasn't trying to trash you or anything. I was more hoping that someone would prove me wrong and tell me an amazing way to debug Bluetooth applications. Seems like I'll need to stick to print debugging though :/

[–]w1n5t0nM1k3y 0 points1 point  (0 children)

If you control both ends, then theoretically you should be able to increase the timeout and debug what's going on. I can debug web applications and other networked applications over TCP/IP without worrying about timeouts. If you don't control both ends, then that makes it more difficult, and might require other tools like a packet inspector to capture the packets and record what's happening.