|
tell me how to live step-debug on 15 year old win CE 6 r3 devices, op
|
#
¿
Oct 20, 2019 15:04
|
|
|
|
| # ¿ May 15, 2024 04:37 |
|
|
The Management posted:install visual studio 6 or whatever it was at the time, get MTP going over a usb connection, live step debug. visual studio had an amazing debugger. realpost: tldr, but suffice to say MTP is seemingly impossible to get working, Hardware took the UART out of the "newest" revision, whatever module provides ActiveSync doesn't work reliably for debugging via IP, and even if by some miracle it DOES all work, the machine is too gutless to run a debug executable at anything other than unreasonable treacle-like speeds. we're on vs2005 for that so when it does work it at least works well, but yeesh what a fuckin farce to get there and god help me if what i need to test is buried behind slow-running actions it's pretty crap but at least it's being greenfielded away to unix boxes in the next year (to Golang [ :| ] )
|
|
#
¿
Oct 20, 2019 15:50
|
|
|
wait this is a quote not edit snipe! noooooooooooooooooo
|
|
#
¿
Oct 20, 2019 15:54
|
|
|
admittedly i have only tried step-debugging a release build on hardware once, but it didn't go well either maybe if I get some spare time I'll try again and get that worked out 
|
|
#
¿
Oct 20, 2019 16:18
|
|
|
suffix posted:the race condition doesn't happen anymore when you attach a debugger these are the worst. someone in the TP thread told me about intel inspector and that thing is really drat slick at finding these and memory problems Ciaphas fucked around with this message at 17:43 on Oct 20, 2019 |
|
#
¿
Oct 20, 2019 17:38
|
|
|
The Management posted:right, activesync not mtp. it’s been a long time since I’ve winced. my experience with it has been pretty good debugging-wise, but I suppose it depends on the BSP. i've been warned lots about golang but tbh it looks overall a lot less foot-shooty than C++ has been in my career so I'm all for it (no generics is a fuckin' grumble tho)
|
|
#
¿
Oct 20, 2019 17:40
|
|
|
also it's not printf it's NKDbgPrintfW, god 
|
|
#
¿
Oct 20, 2019 17:42
|
|
|
rotor posted:one of the last teapot threads before he was permabanned was where he asserted that needing to use a debugger on your code was a sign of weakness and being a bad programmer. technically correct; all programs and programmers are bad
|
|
#
¿
Oct 21, 2019 19:00
|
|
|
Shaggar posted:nah, they should just be taught how to use the debugger a little more than not at all. its really not hard to add a break point to a line and then once they figure out that basic stuff they can be taught how to add conditions and watches. i agree in general, but there's been at least one time for me when a "debugger, just loving break here" in compiled code has worked far better than any amount of fancy watches or break conditions. wish I could remember the details though
|
|
#
¿
Oct 24, 2019 16:51
|
|
|
|
| # ¿ May 15, 2024 04:37 |
|
|
rotor posted:if you're the kind of person that does this, and I think it's fine in moderation, you should also be the kind of person who has a precommit hook to check for the existence of DebugBreak() in the commit I don't but that's because perforce is an arse that I cannot understand the flow or functions of for the life of me bloody drat thing
|
|
#
¿
Oct 24, 2019 18:30
|
|