|
Out of curiosity what made you guys decide to legalize things after so long? And congratulations. 
|
|
|
|
|
Conga-rats!
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
As someone who will be happily married for 30 years come this August, I hope yours lasts as long as mine has.
|
|
|
|
|
Congratulations! I vacationed on PEI many years ago and had the best time.
|
|
|
|
|
Congrats and good luck!
I've been hitched for 32 years, 6 months, 5 days... not that I'm counting. 
|
|
|
|
|
It's okay to count.
The WHY you are counting might not be.
|
|
|
|
|
Allow me to be the first to wish you a happy fiftieth anniversary.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
congrats and good luck.
The first 55 years are the hardest.
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
Wow! Congratulations. Last September we made it to 30 years married. Despite all the married man jokes, it really was the best decision I ever made.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Congrats and enjoy your honeymoon, leave the bloody computer alone!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Wow I had a day off yesterday and missed this.
Félicitations aux heureux mariés ! Enjoy the honeymoon (and all the days after) !
|
|
|
|
|
Congratulations! Live long and prosper!
|
|
|
|
|
I updated Android Studio to the latest.
All kinds of Gradle problems. Android Studio crashed 8 times while trying to build an older project.
Then, the really weird behavior.
Chrome crashed. What!?!
Restarted Chrome.
Chrome crashed again.
Ok, start Firefox.
Crash! -- before you even see the nav bar.
I'm beginning to get scared.
Let's start Edge.
Edge seems okay.
Go to site. Sign in.
Sign in failure. Try again. Edge crashed!!!
Okay, reboot.
Start Chrome. Now, it's not crashing.
Did Android Studio and all that update/crashing weirdness put my system in some odd state?
I think so.
Scary and terrible.
EDIT
One thing I did notice is that the browser client area would flash all black before the crash. It makes me wonder if it was a graphics driver thing related to rendering the page and that is why all the browsers were effected??
Long years ago I had a bad video card that would freeze the screen when I visited one particular site, so a similar weird behavior.
I'll probably never know the answer, but it is weird stuff.
EDIT 2
Looked in Event Viewer and found:
Faulting application name: MicrosoftEdgeCP.exe, version: 11.0.17134.112, time stamp: 0x5b1a453b
Faulting module name: KERNELBASE.dll, version: 10.0.17134.112, time stamp: 0xf2b2cb6c
Exception code: 0x8007000e
Fault offset: 0x000000000003a388
Faulting process id: 0x1358
Faulting application start time: 0x01d40be57c7a3dd2
Faulting application path: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
And then going down further found... (QEMU* is the VM which Android Studio uses to host Android OS emulator)
Faulting application name: qemu-system-i386.exe, version: 0.0.0.0, time stamp: 0xa338a330
Faulting module name: KERNELBASE.dll, version: 10.0.17134.112, time stamp: 0xf2b2cb6c
Exception code: 0xc0000005
Fault offset: 0x0000000000064d90
Faulting process id: 0x8e8
Faulting application start time: 0x01d40bd4ecea3df2
Faulting application path: C:\Users\Roger\AppData\Local\Android\sdk\emulator\qemu\windows-x86_64\qemu-system-i386.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
modified 24-Jun-18 14:50pm.
|
|
|
|
|
Well,
raddevus wrote: Exception code: 0x8007000e
raddevus wrote: Exception code: 0xc0000005
You've posted dozens of these random crashes and event logs over the last year. I really don't understand how you can write books teaching other engineers how to code but just can't seem to debug an out-of-memory exception and access denied error. At first I thought maybe you were an inexperienced engineer but I am beginning to wonder if you just enjoy trolling the lounge.
It honestly seems impossible that you would not know how to debug this. Your articles are very well written and you show a high aptitude for software engineering. It's like meeting a chef at a restaurant that is unable to cook ramen noodles but authored a 300 page cookbook.
Best Wishes,
-David Delaune
modified 24-Jun-18 16:59pm.
|
|
|
|
|
Randor wrote: I really don't understand how you can write books teaching other engineers how to code but just can't seem to debug an out-of-memory exception and access denied error.
Sounds harsh. But, luckily, I am not easily bothered.
Here's the best answer I can offer:
1. I know quite a few things.
2. I don't know _all_ things.
These types of things are low-level system crashes and I'm guessing that few people (a low percentage) out there in the tech community even know these innards of Windows and systems-level programming.
It takes so much time to figure them out.
It is on the level of the carpenter knowing exactly how the raw materials go into making the hammer he uses and then when his hammer fails, he goes to the forge and manufacturers his own hammer head and carves a new hammer handle. He may be a master carpenter, but he ain't doing that.
Windows is a tool! I mean that in the nicest and worsest of ways. 
|
|
|
|
|
raddevus wrote: Sounds harsh. But, luckily, I am not easily bothered.
I apologize if my post bothered you. I am genuinely interested in why some software engineers seem to avoid learning basic debugging skills.
In the last few years I've started noticing a pattern... the same few dozen members seem to repeatedly ask for help in the forums... not just here but also in the other forums I frequent. I'm started to wonder if there is a fundamental psychological reason why some people always ask for help in public forums rather than solve it themselves.
raddevus wrote: It takes so much time to figure them out.
I'd like to learn more about this. Could you tell me more about what you find confusing? Starting with the error logs above... how did you debug this? Did you start by looking up the error codes?
Best Wishes,
-David Delaune
|
|
|
|
|
Randor wrote: I am genuinely interested in why some software engineers seem to avoid learning basic debugging skills.
I actually believe that debugging is one of the most important skills you can learn as a programmer.
But, I debug source code. I don't generally delve into debugging Consumer Products.
Windows Is A Consumer Product
To me, Windows is a Consumer Product. I don't have the source code. I expect it to work properly.
That is a naive view, but think about all the things you use that you would find utterly ridiculous to have to debug.
Do You Debug Your TV?
Suppose you buy an expensive UHD 60" television. When you press the power button you see a lightning bolt flash across the screen. You probably don't think, "Well, here is something I need to debug."
You don't have the schematic to the television and it's going to be difficult. Instead, you probably say, "Hey, BestBuy. I want to return my TV for one that works."
Electronic Hobbies
Now, suppose you were building your own Arduino-based device and it writes to an LCD and it fails. You certainly don't call the Arduino people. Instead, you start figuring out what is wrong.
Windows Is Probably A Balance
Since much of my code resides on top of the Windows system, it behooves me to understand how Windows works. The more the better. But when I'm using Windows as a foundational layer I expect it to work like a consumer product. It's a black box to me.
Why I Post These Types of Things
You also seem to be curious why I post these types of things. It's because I find them interesting. I find that others stumble upon them often and we wonder about them as tertiary incidents. They are side-bars to the direct work I am trying to accomplish.
I see other devs post some interesting video failure or HDD/SSD issues and I keep them in the back of my mind so they are interesting.
But I certainly don't think that when I'm writing a program and I uproot a bug in kernelbase.dll that I should go digging through those system-level calls. We already get far too little done on the project we are working on without descending down those deep layers.
If I am making a direct API call to kernelbase.dll then yes, I would have to deal with that directly.
But, again, I like to think of Windows as a solid foundation beneath me. I believe the OS has finally passed from hobbyist past-time into the professional world.
Good discussion, as always, with you, Randor.
modified 25-Jun-18 0:34am.
|
|
|
|
|
raddevus wrote: Good discussion, as always, with you, Randor.
Sycophancy; I tried to read all that but all I saw was excuses and white noise. You're Fired.
raddevus wrote: But I certainly don't think that when I'm writing a program and I uproot a bug in kernelbase.dll that I should go digging through those system-level calls.
If you ever see a 0x8007000e out-of-memory exception again... it basically means your operating system literally ran out of memory. Everything will begin crashing because memory allocations will begin to fail in every process. Because there is no system memory available all sorts of undefined behaviors will occur.
Might want to look into debugging that.
Best Wishes,
-David Delaune
|
|
|
|
|
Many summers ago, when Win32 was still young, I read a book on Win32 programming. Not the 'Petzold' yet, which I also had next in line. It was something like 'Windows programming in 21 days'. The author repeatedly made the same didactic mistake: He started every 'day' (= chapter) with 'And now we come to one of the most feared parts of windows programming...' or something similar.
At the end of each chapter I was still waiting for the scary part. Most mechanisms seem fundamental and not very complicated by themselves. If you could look at the Windows sourcecode, you would probably be astonished how direct and 'unfancy' it actually is. Nothing to fear if you ever spent some time with a professor that read about OS architecture or read one of his books.
The only 'scary' thing about it actually is the mysticism and supersticion that so many people connect with these things. As if you had to be some sort of evil wizard, trained in the black arts of assembly, C and C++, just to write a dumb driver.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
I'm using AS v3.1.2. No issues with it crashing so far.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
|
|
|
|
|
Yeah this was related to gradle updates and qemu updates that made old Android eumulator images obsolete which ended up crashing Android studio. I hadn't been working t with AS in months so a lot of updates and old project had numerous issues.
|
|
|
|
|
Share the love, the glory: [^]
«... thank the gods that they have made you superior to those events which they have not placed within your own control, rendered you accountable for that only which is within you own control For what, then, have they made you responsible? For that which is alone in your own power—a right use of things as they appear.» Discourses of Epictetus Book I:12
|
|
|
|
|
|
65677 notifications ... 
Didn't think it'd fail, but I missed the Magic Number. Oh well, there's always 4,294,967,295
Might take a while, though. 
Sent from my Amstrad PC 1640
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
With your current rate it will take only an other 7 million(+) months - so better stay sharp not to miss it!
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
