|
Richard Deeming wrote: needs to declare all domains it plans to block in advance; it can't use user-specified rules or dynamically-updated lists to decide which domains should be blocked.
That's ridiculous - like having to specify which viruses a scanner is allowed to detect at installation.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
And here I thought by "dark side" you were gonna say you picked up Generic Programming in C++.
You should. We have cookies.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Cookie (Best cookie monster voice)
Me love cookie 
A home without books is a body without soul. Marcus Tullius Cicero
PartsBin an Electronics Part Organizer - Release Version 1.4.0 (Many new features) JaxCoder.com
Latest Article: EventAggregator
|
|
|
|
|
honey the codewitch wrote: We have cookies.
So do browsers. 
|
|
|
|
|
Browsers are similarly evil.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
It's really not that bad.
I've always refused to commit to Chrome, so I was forced to pick something else when IE was officially declared dead (and more and more pages were now getting broken). I used the original "non-Chromium" version of Edge for maybe a grand total of 45 seconds when it was first introduced years ago.
I'm liking Edge. I can't say which features I use are unique to it since I don't have Chrome installed anywhere so I can't compare, but perhaps first and foremost, I find it does a good job bringing back whatever was opened when you reboot the computer or accidentally close the entire browser instead of just the current tab.
|
|
|
|
|
The thing I like about FF and hate about Chrome is that you can drag a tab to a bookmark. With Chrome you have to hit the bookmark icon then wander through the choices and save. It's a lot easier to just drag it where you want it.
Haven't tried it with edge.
The only thing I don't like about FF is I can't do online banking with my bank, it gives all kinds of errors when I try to log on so am forced to used Edge.
A home without books is a body without soul. Marcus Tullius Cicero
PartsBin an Electronics Part Organizer - Release Version 1.4.0 (Many new features) JaxCoder.com
Latest Article: EventAggregator
|
|
|
|
|
I can't say I've tried to save a URL as a favorite by dragging. I always use the Add to Favorites button, then pick the correct folder in the resulting popup. Re-organizing existing URLs by drag and drop--that, however, I do all the time and I find it works well enough.
|
|
|
|
|
We have a customer for whom we've done a [great steaming] pile of custom work. A couple of times a year they find a problem with the custom stuff. It always turns into a wretched slog through a Lovecraftian swamp of bubbling ichor (e.g. legacy code) I didn't write but am now required to maintain. Three months ago they reported an issue with one of their features in the new generation of product that didn't happen with the old one. I compared the code between the two and it was identical. I've spent considerable hours debugging through the code for the feature.
It turns out the new code is looking in the wrong place in the registry to see if their custom features are enabled  . The old code only worked accidently.
Cue the fireworks a day early, and let the naked happy dance ![Jig | [Dance]](https://www.codeproject.com/script/Forums/Images/jig.gif) commence!
Software Zen: delete this;
|
|
|
|
|
One of our embedded systems has been around for 15+ years, we had one or two customers in that time have random device crashes. We tried setting things up and using the customers configuration, to no avail, for many months. Data from the clients revealed the crashes occur at many different addresses. Finally, in desperation, I decided to look at stack usage. There were two routines related to little used features out of hundreds (think 70-80K lines of code in assembler) that allocated 4 bytes more stack space than it deallocated. It took thousands of these routine calls before encroaching on runtime variables. Twas a happy day when I found it ![Beer | [beer]](https://codeproject.freetls.fastly.net/script/Forums/Images/beer.gif) , and as important, a big learning experience.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
jeron1 wrote: Twas a happy day when I found it ![Beer | [beer]](https://www.codeproject.com/script/Forums/Images/beer.gif) , and as important, a big learning experience
Same here. I've had other memorable bugs that were excruciating to recreate and diagnose. One was a GDI handle leak that took over a week of run time to show up and crash the application. Another was a piece of embedded code where the TCP/IP code we bought back in 1995 did not re-initialize properly after a network hardware error. Both of these took weeks of debugging to find and reproduce and only a couple of hours to correct.
Software Zen: delete this;
|
|
|
|
|
Gary Wheeler wrote: Both of these took weeks of debugging to find and reproduce and only a couple of hours to correct.
Funny how that is. 
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Now imagine weeks of debugging and seconds for the actual fix (after the problem was identified and well understood).
|
|
|
|
|
True, it's tough when you are going through it, for me sleepless nights are the usual result!
dandy72 wrote: after the problem was identified and well understood
To me there's a certain satisfaction to that, as rough as the road was to get to that point (and maybe learning a thing or two about better implementation, as I did).
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
I get what you say, but the last time such a thing happened to me it was a case of a missing quote in a string that was being built with multiple layers of escaping them. So of course the compiler didn't know any better and was of no help.
There was nothing satisfying about solving that particular problem. Just annoyance at whoever last modified the string in the first place...
|
|
|
|
|
My favorite was a 49-day crash bug caused by a 32-bit timer rollover. Management wanted to know why test did not find this bug.
|
|
|
|
|
You always find something in the last place you look for it.
|
|
|
|
|
My takeaway is "don't write things in assembly" 
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
I wouldn't necessarily argue!  In this particular product there's a lot of time sensitive code, and over the years it's grown, A LOT.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Hopefully you bill by the hour.
|
|
|
|
|
Unfortunately no  , at least in my day job.
Software Zen: delete this;
|
|
|
|
|
Wait, you said the code was identical between the new and old versions of the product.
So how is there a difference that caused it to look in the wrong place?
UNLESS, it was always looking in the wrong place, and changes to the surrounding code put the information into a different place that it was unable to find by accident?
OR, are you saying that the code that just turned the feature on didn't work, and the code of the feature itself was unchanged?
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
The difference was in a class used throughout the product to access the registry. This component (a Windows service) used that class incorrectly in the old product but still managed to find the values at the appropriate key. When the service was migrated to the new product (which changes the registry key used), its incorrect usage of the registry class caused it to look at the incorrect registry key and not find the required values.
In both cases, the service and the registry class, they looked correct on inspection. It wasn't until I stepped through the service that I discovered it was assuming certain things about the registry class weren't true and never had been. FWIW, I didn't write either of them.
Software Zen: delete this;
|
|
|
|
|
|
Yup .
Software Zen: delete this;
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
