Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Its Friday, you all know what that means! ... Its results day for practiseSafeHex's most incompetent co-worker!!!
*audience: wwwwwwooooooooo!!!!*
We've had a bewildering array of candidates, lets remind ourselves:
- a psychopath that genuinely scared me a little
- a CEO I would take pleasure seeing in pain
- a pothead who mistook me for his drug dealer
- an unbelievable idiot
- an arrogant idiot obsessed with strings
Tough competition, but there can be only one ... *drum roll* ... the winner is ... none of them!
*audience: GASP!*
*audience member: what?*
*audience member: no way!*
*audience member: your fucking kidding me!*
Sir calm down! this is a day time show, no need for that ... let me explain, there is a winner ... but we've kept him till last and for a good reason
*audience: ooooohhhhh*
You see our final contestant and ultimate winner of this series is our good old friend "C", taking the letters of each of our previous contestants, that spells TRAGIC which is the only word to explain C.
*audience: laughs*
Oh I assure you its no laughing matter. C was with us for 6 whole months ... 6 excruciatingly painful months.
Backstory:
We needed someone with frontend, backend and experience with IoT devices, or raspberry PI's. We didn't think we'd get it all, but in walked an interviewee with web development experience, a tiny bit of Angular and his masters project was building a robot device that would change LED's depending on your facial expressions. PERFECT!!!
... oh to have a time machine
Working with C:
- He never actually did the tutorials I first set him on for Node.js and Angular 2+ because they were "too boring". I didn't find this out until some time later.
- The first project I had him work on was a small dashboard and backend, but he decided to use Angular 1 and a different database than what we were using because "for me, these are easier".
- He called that project done without testing / deploying it in the cloud, despite that being part of the ticket, because he didn't know how. Rather than tell or ask anyone ... he just didn't do it and moved on.
- As part of his first tech review I had to explain to him why he should be using if / else, rather than just if's.
- Despite his past experience building server applications and dashboards (4 years!), he never heard of a websocket, and it took a considerable amount of time to explain.
- When he used a node module to open a server socket, he sat staring at me like a deer caught in headlights completely unaware of how to use / test it was working. I again had to explain it and ultimately test it for him with a command line client.
- He didn't understand the need to leave logging inside an application to report errors. Because he used to ... I shit you not ... drive to his customers, plug into their server and debug their application using a debugger.
... props for using a debugger, but fuck me.
- Once, after an entire 2 days of tapping me on the shoulder every 15 mins for questions / issues, I had to stop and ask:
Me: "Have you googled it?"
C: "... eh, no"
Me: "can I ask why?"
C: "well, for me, I only google for something I don't know"
Me: "... well do you know what this error message means?"
C: "ah good point, i'll try this time"
... maybe he was A's stoner buddy?
- He burned through our free cloud usage allowance for a month, after 1 day, meaning he couldn't test anything else under his account. He left an application running, broadcasting a lot of data. Turns out the on / off button on the dashboard only worked for "on". He had been killing his terminal locally and didn't know how to "ctrl + c a cloud app" ... so left it running. His intention was to restart the app every time you are done using it ... but forgot.
- His issue with the previous one ... not any of his countless mistakes, not the lack of even trying to make the button work, no, no, not for C. C's issue is the cloud is "shit" for giving us such little allowances. (for the record in a month I had never used more than 5%).
- I had to explain environment variables and why they are necessary for passwords and tokens etc. He didn't know it wasn't ok to commit these into GitHub.
- At his project meetups with partners I had to repeatedly ask him to stop googling gifs and pay attention to the talks.
- He complained that we don't have 3 hour lunch breaks like his last place.
- He once copied and pasted the same function 450 times into a file as a load test ... are loops too mainstream nowadays?
You see C is our winner, because after 6 painful months (companies internal process / requirements) he actually achieved nothing. I really mean that, nothing. Every thing was so broken, so insecure / wide open, built without any kind of common sense or standards I had to delete it all and start again ... it took me 2 weeks.
I hope you've all enjoyed this series and will join me in praying for the return of my sanity ... I do miss it a lot.
Yours truly,
practiseSafeHex21 -
*Lazy Friend has IntelliJ and Eclipse*
*Lazy Friend using Notepad++*
Me: Why don't you use IntelliJ? Its debugger really helps..
LF: It takes too much time to start, I don't have that much time..
*continues staring at his screen and using his mind debugger*
It's kinda funny when he just sits and stares at his screen after saying that he doesn't have any time..
It took way less time to find the (a?) bug when he finally used the debugger..7 -
I thought I was really good at debugging. Then I met this legend in my workplace. And he was like...
5 -
What's the worst bug? Schrödinger's bug, one that only appears when the debugger is not attached, and your test instruments are disabled.12
-
Fuck you fucking piece of self taught shit. Self taught my ass you dont even know how to use git or how to use modern IDE. You dont even know how to use debugger. You dont read other peoples code because you are an arrogant kid who thinks that everybody elses code is trash. Yet after couple days when you need to work on your own code you usually rewrite entire fucking thing because of how fucked up your spaghetti implementations are. Even worse you dont even know fucking english so documentation is useless to you unless I dumb down everything for you and spoon feed you like a 5 year old. Motherfucker you cant even stick to a proper work schedule, you go to sleep at 7am and wake up at 18.00 and I have to fucking work overtime because Im blocked by your spaghetti code. Fuck you fucking self taught arrogant piece of shit who never ever worked as a dev profesionally yet you have the nerve to feel cocky.32
-
I actually talked to my duck. He solved my Server 500 error which said "java.lang.NoSuchFieldError: logger". I had to purge the build .class files and recompile the application and low and behold it runs.
Why is my duck a better debugger than most actual debuggers? He didn't even go to college!
11 -
Today I became a rubber duck debugger 🐤
I was leaving from office and spotted my senior collegue sitting glued to the screen solving an issue. I sat along with him to embark on a debug adventure. I casually asked him about the issue and what might cause it. After a bit of discussion *bam* he figured out where the problem lies and solved it in an instant.
Quack quack off I run 🐤5 -
Most of the code I write nowadays is for GPUs using a dialect of C. Anyways, due to the hardware of GPUs there is no convenient debugger and you can't just print to console neither.
Most bugs are solved staring at the code and using pen and paper.
I guess one could call that a quirk.12 -
I just spent an hour debugging my company's web app. More specifically, I was trying to fix a bug that made a label on a comment I just made say "Posted 3 days ago".
After confirming timestamps on the server are correct with a calculator, fiddling around with the js debugger, and ruling out weird timezone-related shenanigans, I came to a conclusion.
The bug was in fact sitting, quite comfortably, between the chair and the keyboard.
Yesterday I had moved the date on my computer roughly 3 days into the future, because I was testing out some unrelated code that was dealing with Redis, and I wanted to expire all of the keys stored inside of it.
Don't blame me, my parents told me I had fallen onto my head as a child.5 -
Does anyone here feel like they're more of a debugger than a programmer ?
Like 70% of my time is spent investigating / fixing bugs and anomalies.13 -
Insecure... My laptop disk is encrypted, but I'm using a fairly weak password. 🤔
Oh, you mean psychological.
Working at a startup in crisis time. Might lose my job if the company goes under.
I'm a Tech lead, Senior Backender, DB admin, Debugger, Solutions Architect, PR reviewer.
In practice, that means zero portfolio. Truth be told, I can sniff out issues with your code, but can't code features for shit. I really just don't have the patience to actually BUILD things.
I'm pretty much the town fool who angrily yells at managers for being dumb, rolls his eyes when he finds hacky code, then disappears into his cave to repair and refactor the mess other people made.
I totally suck at interviews, unless the interviewer really loves comparing Haskell's & Rust's type systems, or something equally useless.
I'm grumpy, hedonistic and brutally straight forward. Some coworkers call me "refreshing" and "direct but reasonable", others "barely tolerable" or even "fundamentally unlikable".
I'm not sure if they actually mean it, or are just messing with me, but by noon I'm either too deep into code, or too much under influence of cognac & LSD, wearing too little clothing, having interesting conversations WITH instead of AT the coffee machine, to still care about what other humans think.
There have been moments where I coded for 72 hours straight to fix a severe issue, and I would take a bullet to save this company from going under... But there have also been days where I called my boss a "A malicious tumor, slowly infecting all departments and draining the life out of the company with his cancerous ideas" — to his face.
I count myself lucky to still have a very well paying job, where many others are struggling to pay bills or have lost their income completely.
But I realize I'm really not that easy to work with... Over time, I've recruited a team of compatible psychopaths and misfits, from a Ukranian ex-military explosives expert & brilliant DB admin to a Nigerian crossfitting gay autist devops weeb, to a tiny alcoholic French machine learning fanatic, to the paranoid "how much keef is there in my beard" architecture lead who is convinced covid-19 is linked to the disappearance of MH370 and looks like he bathes in pig manure.
So... I would really hate to ever have to look for a new employer.
I would really hate to ever lose my protective human meat shield... I mean, my "team".
I feel like, despite having worked to get my Karma deep into the red by calling people all kinds of rude things, things are really quite sweet for me.
I'm fucking terrified that this peak could be temporary, that there's a giant ravine waiting for me, to remind me that life is a ruthless bitch and that all the good things were totally undeserved.
Ah well, might as well stay in character...
*taunts fate with a raised middlefinger*13 -
(don't mind the first sentence of the img)
This is what i tell my debugger each time i run an application...
-
Very specific and annoying situation here:
- Working on a machine learning project with other people
- I'm on Linux, they use Windows
- We code in python
- We generally use vscode for development, and its python extension
I implement some basic neural networks with tensorflow, and add a bunch of logging for it. I test it on my machine and it works fine.
But, my group mates report that "after a few seconds the entire client hangs".
Apparently it only happens on Windows?
We start debugging the hell out of the code I implemented, added 20 log messages and sat there for a solid hour.
Until I make one very odd realization: the issue doesn't happen when I run the script in my terminal, instead of vscode with the debugger. So I try different debug settings, using an external terminal instead of vscode's built in debug console seems to fix it too.
And I make another observation: In the debug console, some messages don't seem to appear at all, while the external terminal shows them just fine.
So, turns out, that printing an epsilon character: “ε” (U+03B5), causes the entire thing to hang up.
It's the year 2020 and somehow we still can't do unicode.
I'm so done, what on earth.9 -
The problem with working on a debugger for a living is that you can end up debugging a debugger debugging a debugger that is remotely debugging a debugger which is debugging a program...
...only to find out there's a bug in the first debugger and you need to debug it.
4 -
!rant
I was told to take a day's rest without putting in a leave because of the number of hours I've been putting in. And for beating the shit out of deadlines.
Damn it feels good to be appreciated!5 -
Today I used a debugger for the first time and holy fuck it's magical why didn't I do this sooner..8
-
writing library code is hard.
there are sooo many details that go into writing good libraries:
designing intuitive and powerful apis
deciding good api option defaults, disallowing or warning for illegal operations
knowing when to throw, knowing when to warn/log
handling edge cases
having good code coverage with tests that doesn't suck shit, while ensuring thry don't take a hundred years to run
making the code easy to read, to maintain, robust
and also not vulnerable, which is probably the most overlooked quality.
"too many classes, too little classes"
the functions do too much it's hard to follow them
or the functions are so well abstracted, that every function has 1 line of code, resulting in code that is even harder to understand or debug (have fun drowning in those immense stack traces)
don't forget to be disciplined about the documentation.
most of these things are
deeply affected by the ecosystem, the tools of the language you're writing this in:
like 5 years ago I hated coding in nodejs, because I didn't know about linters, and now we have tools like eslint or babel, so it's more passable now
but now dealing with webpack/babel configs and plugins can literally obliterate your asshole.
some languages don't even have a stable line by line debugger (hard pass for me)
then there's also the several phases of the project:
you first conceive the idea, the api, and try to implement it, write some md's of usage examples.
as you do that, you iterate on the api, you notice that it could better, so you redesign it. once, twice, thrice.
so at that point you're spending days, weeks on this side project, and your boss is like "what the fuck are you doing right now?"
then, you reach fuckinnnnng 0.1.0, with a "frozen" api, put it on github with a shitton of badges like the badge whore you are.
then you drop it on forums, and slack communities and irc, and what do you get?
half of the community wants to ban you for doing self promotion
the other half thinks either
a) your library api is shitty
b) has no real need for it
c) "why reinvent the wheel bruh"
that's one scenario,
the other scenario is the project starts to get traction.
people start to star it and shit.
but now you have one peoblem you didn't have before: humans.
all sorts of shit:
people treating you like shit as if they were premium users.
people posting majestically written issues with titles like "people help, me no work, here" with bodies like "HAAAAAAAAAALP".
and if you have the blessing to work in the current js ecosystem, issues like "this doesn't work with esm, unpkg, cdnjs, babel, webpack, parcel, buble, A BROWSER".
with some occasional lunatic complaining about IE 4 having a very weird, obscure bug.
not the best prospect either.4 -
Just bought a subscription for JetBrains.
Trying CLion debugger...
THIS SH*T IS AMAZING
Me: I love you, I love you, I love you
Computer:
Me: 😍😍😍
Computer:
Me: (Hugs computer)10 -
Attach the debugger - software runs
Remove the debugger - software doesn’t run
Happy Debugging...
debugging without being able to attach a debugger?! Sounds like a long day, if not even days...7 -
Interesting bug hunt!
Got called in because a co-team had a strange bug and couldn't make sense of it. After a compiler update, things had stopped working.
They had already hunted down the bug to something equivalent to the screenshot and put a breakpoint on the if-statement. The memory window showed the memory content, and it was indeed 42. However, the debugger would still jump over do_stuff(), both in single step and when setting a breakpoint on the function call. Very unusual, but the rest worked.
Looking closer, I noticed that the pointer's content was an odd number, but was supposed to be of type uint32_t *. So I dug out the controller's manual and looked up the instruction set what it would do with a 32 bit load from an unaligned address: the most braindead thing possible, it would just ignore the lowest two address bits. So the actual load happened from a different address, that's why the comparison failed.
I think the debugger fetched the memory content bytewise because that would work for any kind of data structure with only one code path, that's how it bypassed the alignment issue. Nice pitfall!
Investigating further why the pointer was off, it turned out that it pointed into an underlying array of type char. The offset into the array was correctly divisible by 4, but the beginning had no alignment, and a char array doesn't need one. I checked the mapfiles and indeed, the old compiler had put the array to a 4 byte boundary and the new one didn't.
Sure enough, after giving the array a 4 byte alignment directive, the code worked as intended.
8 -
Debugger...Chicken I guess? Got it from one of my students last year. Adapter for scale. It's not the size that matters...
2 -
Went to my boss to tell him that I will be leaving by the end of the year. Apparently he had similar plans and pretty soon we were discussing where he can go to!5
-
Achievement unlocked: malloc failed
😨
(The system wasn't out of memory, I was just an idiot and allocated size*sizeof(int) to an int**)
I'd like to thank myself for this delightful exercise in debugging, the GNU debugger, Julian Seward and the rest of the valgrind team for providing the necessary tools.
But most of all, I'd like that three hours of my life back 😩4 -
[long]
When searching for internship via school I found this small startup with this cute project of building a teaching tool for programming. There were back then 2 programmers: the founder and the co-founder.
Then like 1 week before the internship started, the co-founder had a burnout and had to get off the project, while the company was so low on budget the founder, aka my new b0ss, had to work separate jobs to keep the company alive. (quite metal tbh)
It's funny because I'm a junior developer, 100%. I've been coding as a hobby for around 8 years now but I've never worked in a big company before. (No exception to this workplace either)
First project I get: rewrite the compiler. The Python compiler.
"But wait, why not just embed a real compiler from the first case?"
-nanananana it's never simple, as you probably know from your own projects.
The new compiler, as compared to existing embedded compiler solutions out there, needed these prime features:
- Walk through the code (debugger style), but programmatically.
- Show custom exceptions (ex: "A colon is needed at the end of an if-statement" instead of "Syntax error line 3")
- Have a "Did-you-mean this variable?" error for usage of unassigned variables.
- Be able to be embedded in Unity's WebGL build target
All for the use case of being a friendly compiler.
The last dash in the list is actually the biggest bottleneck which excluded all existing open-source projects (i could find). Compliant with WebAssembly I can't use threads among other things, IL2CPP has lots of restrictions, Unity has some as well...
Oh and it should of course be built using test-driven development.
"Good luck!" - said the founder, first day of work as she then traveled to USA for **3 weeks**, leaving me solo with the to-be-made codebase and humongous list of requirements.
---
I just finished the 6th week of internship, boss has been at "HQ" for 3 weeks now, and I just hit the biggest milestone yet for this project.
Yes I've been succeeding! This project has gone so well, and I'm surprising myself how much code I've been pumping out during these weeks.
I'm up now at almost 40'000 lines of source and 30'000 lines of code. ‼
( Biggest project I've ever worked on previously was at 8'000 lines of code )
The milestone (that I finished today) was for loops! As been trying to showcase in the GIF.
---
It's such a giant project and I can honestly say I've done some good work here. Self-five. Over-performing is a thing.
The things that makes me shiver though is that most that use this application will never know the intricates of it's insides, and the brain work put into it.
The project is probably over-engineered. A lot. Having a home-made compiler gives us a lot of flexibility for our product as we're trying to make more of a "pedagogic IDE". But no matter that I reinvented the wheel for the 105Gth time, it's still the most fun I've had with a project to date.
---
Also btw if anyone wants to see source code, please give me good reasons as I'm actively trying to convince my boss to make the compiler open-source.
Cheers!
4 -
1. attach a debugger
2. create a set of breakpoints
3. perform an action in the UI
4. breakpoint is hit. F9 to jump to another breakpoint
5.
...
.......
...........
................
....................
nothing............
even more of nothing.....
......................................................
6. Kill the app. Restart. Repeat. Nothing again. Repeat it all ~5 times. Give up.
7. Go get some tea.
8. Come back with a cup of hot tea
9. the _next_ breakpoint is now hit (º . º)
10. F9 - yet another breakpoint is hit.
11. contemplate your own mental state, considering the #6
9 -
THIS FUCKING DEBUGGER IS IGNORING MY FUCKING BREAKPOINTS
GO TO HELL YOU PIECE OF SHIT
AND RSPEC: FUCK YOUR LIMITED METHOD HIT-COUNTING BULLSHIT! ONE HIT-COUNT PER METHOD FOR THE ENTIRE SPEC IS NOT GOOD ENOUGH!
FJA;KLGAKLGJFKSDHG18 -
today I experienced real-time bug fixing and deployment..
The phone was attached to the debugger, the client is using the app, me catching the logs.
Client: oh here is wrong behavior.
Me: *tapping on keyboard, then* ok try now please..
😅2 -
Finally fixing a 16 hour bug that was harassing my thoughts is a very good feeling.
Sleep is the ultimate debugging debugger.1 -
So recently I did a lot of research into the internals of Computers and CPUs.
And i'd like to share a result of mine.
First of all, take some time to look at the code down below. You see two assembler codes and two command lines.
The Assembler code is designed to test how the instructions "enter" and "leave" compare to manually doing what they are shortened to.
Enter and leave create a new Stackframe: this means, that they create a new temporary stack. The stack is where local variables are put to by the compiler. On the right side, you can see how I create my own stack by using
push rbp
mov rbp, rsp
sub rsp, 0
(I won't get into details behind why that works).
Okay. Why is this even relevant?
Well: there is the assumption that enter and leave are very slow. This is due to raw numbers:
In some paper I saw ( I couldn't find the link, i'm sorry), enter was said to use up 12 CPU cycles, while the manual stacking would require 3 (push + mov + sub => 1 + 1 + 1).
When I compile an empty function, I get pretty much what you'd expect just from the raw numbers of CPU cycles.
HOWEVER, then I add the dummy code in the middle:
mov eax, 123
add eax, 123543
mov ebx, 234
div ebx
and magically - both sides have the same result.
Why????
For one thing, there is CPU prefetching. This is the CPU loading in ram before its done executing the current instruction (this is how anti-debugger code works, btw. Might make another rant on that). Then there is the fact that the CPU usually starts work on the next instruction while the current instruction is processing IFF the register currently involved isnt involved in the next instruction (that would cause a lot of synchronisation problems). Now notice, that the CPU can't do any of that when manually entering and leaving. It can only start doing the mov eax, 1234 while performing the sub rsp, 0.
----------------
NOW: notice that the code on the right didn't take any precautions like making sure that the stack is big enough. If you sub too much stack at once, the stack will be exhausted, thats what we call a stack overflow. enter implements checks for that, and emits an interrupt if there is a SO (take this with a grain of salt, I couldn't find a resource backing this up). There are another type of checks I don't fully get (stack level checks) so I'd rather not make a fool of myself by writing about them.
Because of all those reasons I think that compilers should start using enter and leave again.
========
This post showed very well that bare numbers can often mislead.
24 -
On my first week in the internship, I have to create a small website and it has to be finished ASAP. So I used Bootstrap.
After finishing I tested the website in chrome debugger tools for every screen size (design responsiveness), it was working fine. My stupidity was that I haven't tested on actual mobile/tablet.
The site was live, I send the link to one of my friends and he said "why everything is so small? looks like I'm browsing on PC". I quickly grab my phone and visited the site and it was not responsive on mobile. Started to check the code again, tested again on chrome tools it was working. But not on mobile. Changed the bootstrap file but no fucking changes on mobile.
After few moments of thinking, I realized that I haven't included the "meta viewport" tag. I felt so stupid and it was kind of embarrassing for me.
Now I first include meta tags before working on new project.5 -
Do you ever have those weeks where you have to fix a bug, then uncover another bug then another then another. Then you realise some functionality is completely missing. You write tests to cover your bug fixes and new functionality. Then you realise tests are broken with your fixes and you have no idea why. Then you get so frustrated you start making silly mistakes. Then your debugger starts playing up.... Yeah that's been my week.5
-
Bad dev habit: using a bazillion console.log/println like a caveman instead of using a proper debugger.9
-
Took me 6+ full days.
The feature does not work. Repro is unknown, so only prod is experiencing the issue.. Which rules out the debugger option. Sometimes there's an entry seen in logs: "java.lang.StringIndexOutOfBoundsException". Nothing more - just that. No stack, no class, no nothing. Is it my code that's buggy? Is it some config? Integration? Unexpected response...? A bug in a lib? Is dimm faulty ir maybe server's shared libs are off?
Turns out I used a closing parentheses instead a closing curly bracket in an error message that's supposed to be interpolated...
String message = "{some-business-rule-related-error-message-key)";
took me 6+ full days... But I found it. Took the rest of that Friday off to walk in a park and enjoy my life :)10 -
Debugging assembly without a debugger.... Also, I am very new to this so it's even worse.
Only 2 hours until I can find some wifi to get gdb...
Fun times..7 -
I propose that the study of Rust and therefore the application of said programming language and all of the technology that compromises it should be made because the language is actually really fucking good. Reading and studying how it manages to manipulate and otherwise use memory without a garbage collector is something to be admired, illuminating in its own accord.
BUT going for it because it is a "beTter C++" should not constitute a basis for it's study.
Let me expand through anecdotal evidence, which is really not to be taken seriously, but at the same time what I am using for my reasoning behind this, please feel free to correct me if I am wrong, for I am a software engineer yes, I do have academic training through a B.S in Computer Science yes, BUT my professional life has been solely dedicated to web development, which admittedly I do not go on about technical details of it with you all because: I am not allowed to(1) and (2)it is better for me to bitch and shit over other petty development related details.
Anecdotal and otherwise non statistically supported evidence: I have seen many motherfuckers doing shit in both C and C++ that ADMIT not covering their mistakes through the use of a debugger. Mostly because (A) using a debugger and proper IDE is for pendejos and debugging is for putos GDB is too hard and the VS IDE is waaaaaa "I onlLy NeeD Vim" and (B) "If an error would have registered then it would not have compiled no?", thus giving me the idea that the most common occurrences of issues through the use of the C father/son languages come from user error, non formal training in the language and a nice cusp of "fuck it it runs" while leaving all sorts of issues that come from manipulating the realm of the Gods "memory".
EVERY manual, book, coming all the way back to the K&C book talks about memory and the way in which developers of these 2 languages are able to manipulate and work on it. EVERY new standard of the ISO implementation of these languages deals, through community effort or standard documentation about the new items excised through features concerning MODERN (meaning, no, the shit you learned 20 years ago won't fucking cut it) will not cut it.
THUS if your ass is not constantly checking what the scalpel of electrical/circuitry/computational representation of algorithms CONDONES in what you are doing then YOU are the fucking problem.
Rust is thus no different from the original ideas of the developers behind Go when stating that their developers are not efficient enough to deal with X language, Rust protects you, because it knows that you are a fucking moron, so the compiler, advanced, and well made as it is, will give you warnings of your own idiotic tendencies, which would not have been required have you not been.....well....a fucking idiot.
Rust is a good language, but I feel one that came out from the necessity of people writing system level software as a bunch of fucking morons.
This speaks a lot more of our academic endeavors and current documentation than anything else. But to me DEALING with the idea of adapting Rust as a better C++ should come from a different point of view.
Do I agree with Linus's point of view of C++? fuck no, I do not, he is a kernel engineer, a damn good one at that regardless of what Dr. Tanenbaum believes(ed) but not everyone writes kernels, and sometimes that everyone requires OOP and additions to the language that they use. Else I would be a fucking moron for dabbling in the dictionary of languages that I use professionally.
BUT in terms of C++ being unsafe and unsecured and a horrible alternative to Rust I personaly do not believe so. I see it as a powerful white canvas, in which you are able to paint software to the best of your ability WHICH then requires thorough scrutiny from the entire team. NOT a quick replacement for something that protects your from your own stupidity BY impending the use of what are otherwise unknown "safe" features.
To be clear: I am not diminishing Rust as the powerhouse of a language that it is, myself I am quite invested in the language. But instead do not feel the reason/need before articles claiming it as the C++ killer.
I am currently heavily invested in C++ since I am trying a lot of different things for a lot of projects, and have been able to discern multiple pain points and unsafe features. Mainly the reason for this is documentation (your mother knows C++) and tooling, ide support, debugging operations, plethora of resources come from it and I have been able to push out to my secret project a lot of good dealings. WHICH I will eventually replicate with Rust to see the main differences.
Online articles stating that one will delimit or otherwise kill the other is well....wrong to me. And not the proper approach.
Anyways, I like big tits and small waists.16 -
If you're good at the debugger it means you spent a lot of time debugging. I don't want you to be good at the debugger.
- Uncle Bob2 -
For fucks sake python.
Reminder to the morons like me still using python:
Notepad++ is not a real IDE and Console output is not a real debugger.
And here we see the absolutely dogshit worthless error output of python:
Says its the fucking return line where the problem is. Besides the problem being between my fucking ears apparently, it took a fucking double take to realize I had capitalized the class keyword.
16 -
@trogus it would be pretty rad to have an avatar option that would add a devRant sticker to a laptop.
btw: I love the Rubik's cube chillin with the rubber ducking debugger.
3 -
I am so tired of dealing with incompetence in every area of my life here. Everyone is fucking up all at the same time and I'm getting stressed out to the point of sickness because of it. I ranted about my colleague who used me as his personal debugger. Areas outside of work fucking sucks too.
My aircon keeps leaking. I had it cleaned up several times before. Repair crew said it needed to be cleaned up more frequently since I started working from home. Okay, fine. Eventually, the board below it had to be replaced due to water damage. Same shit all over again and eventually, the unit had to be repaired. After said repair, it started leaking again a few days later. I am sick and it's hot as ever here.
My orthodontist is clumsy. Every time I had to go to her for readjusment, her hands would slip and hit my lips, teeth, and jaw. Cut out rubber would sometimes hit my face. Just the way she fucking moves is so careless and she's the only certified ortho here. She would say sorry but it happened so many times in every session that I don't think it's normal. Yesterday, she replaced the wire and just a few minutes later, it fell off. She only asked me if I can feel something stabbing my cheek, I said no because there is none. Apparenlty, she didn't check if the wire is loose. Something I cannot see for myself but on my next visits, I'll have to remind her of her job.
I am so tired. I am sick right now and had to deal with all this shit. I tried to be patient but at this point, I feel taken advantage of for that. I try to deal with these people in a civil manner and not be a Karen but at this point, I don't think they'll take me seriously unless I'm already angry and I absolutely hate being angry. Anger is exhausting to me and hard to control when I get to the point of rage. I am asking for the workers to repair my aircon for free because they didn't fix it the first few times or else I'm gonna file a complaint. If they fucking say no, god bless their soul because I will end them.
Why are people like this? Do you get off making others suffer for your incompetence? When you fuck up so many times, don't you ever think "Hey, maybe I should do better." I am extremely stressed out. I woke up sick and didn't get shit done. That alone makes me feel guilty and want to make up for it. How about these fuckers? I don't want to care anymore. I don't want to be angry anymore but this place is so hopeless and I've had too many experience of this that I'm starting to get off on the idea of it burning to the ground like it's supposed to. Erased from the map and forgotten.10 -
!rant
Today, my true developer saga begins. First job as an embedded developer and I am prepared with my flaming dark themed rubber duck debugger. What could go wrong? :D
3 -
So our new teacher executes console applications (C#, .NET) with the VS debugger attached (F5) instead of just letting it execute normally (CTRL + F5).
He complained about the output not showing up (he still gave me full score at least) That's because executing with F5 simply ends the program after Main() is done executing, while CTRL + F5 leaves the window open until you press a key, saying "Press any key..."
So here's what I'm gonna put at the very bottom of Main() in future:
if (System.Diagnostics.Debugger.IsAttached)
{
Console.CursorVisible = false;
Console.WriteLine("Press any key...");
Console.ReadKey(true);
}5 -
With the brand new Microsoft C++ compiler, what you see in the debugger, is not always what you get...
8 -
If anyone has been keeping up with my data warehouse from hell stories, we're reaching the climax. Today I reached my breaking point and wrote a strongly worder email about the situation. I detailed 3 separate cases of violated referential integrity (this warehouse has no constraints) and a field pulling from THE WRONG FLIPPING TABLE. Each instance was detailed with the lying ER diagram, highlighted the violating key pairs, the dangers they posed, and how to fix it. Note that this is a financial document; a financial document with nondeterministic behavior because the previous contractors' laziness. I feel like the flipping harbinger of doom with a cardboard sign saying "the end is near" and keep having to self-validate that if I was to change anything about this code, **financial numbers would change**, names would swap, description codes would change, and because they're edge cases in a giant dataset, they'll be hard to find. My email included SQL queries returning values where integrity is violated 15+ times. There's legacy data just shoved in ignoring all constraints. There are misspellings where a new one was made instead of updating, leaving the pk the same.
Now I'd just put sorting and other algos, but the data is processed by a crystal report. It has no debugger. No analysis tools. 11 subreports. The thing takes an hour to run and 77k queries to the oracle backend. It's one of the most disgusting infrastructures I've ever seen. There's no other solution to this but to either move to a general programming language or get the contractor to fix the data warehouse. I feel like I've gotten nowhere trying to debug this for 2 months. Now that I've reached what's probably the root issue, the office beaucracy is resisting the idea of throwing out the fire hazard and keeping the good parts. The upper management wants to just install sprinklers, and I'm losing it. -
Does most memorable in a bad way count? 🤔
He left almost 2 years ago..or even more.. left a bunch of bugs and logical fuckups for me to fix.. some already fixed, some still lingering there..
I want to not blame him for everything, since we lack proper code review protocols and all.. but I've asked on several occasions if he understands the problem and what must be done..and the answer was always yes..results, after I got time to check up on him, the code he wrote was most probably copy pasted from stack overflow or somewhere else.. butchered in any and every way possible..
And of course already checked in to TFS.. along with bunch of files that were not even changed (he didn't bother to check that and exclude them) + a bunch of files from other projects... Told him to not do that on several occasions too, but he still managed to fuck things up this way.. leaving all the uncommented debugger; crap and alerts in the js files..
On one occasion I was working on new GUI..api part I already finished..got the order from above to delegate this to him as it is not much he can fuck up so I could focus on more important & complex stuff..
Maybe additional 4h of work + testing for everything..
I show him the prepared files, one controller, one view..explained what parts of code goes where etc.. a little short of writing everything myself.. Ask if he understands what needs to be done & how and told him if he has any problems/questions to ask me asap..
Said he understood what needs to be done.. after a day or two he asks me why something is not workig as expected.. I check the files, correct initialization was commented out and all the code was stuffed in the view file.. Took him another day to move the code to proper files.. Not sure about the possible bugs left there as the client later decided that they will not be using this..
I later found out that years of C# experience on his CV was actually a school course.. he didn't even know why the changes on api are not showing up..because he didn't know that he has to build the code..
I mean, if he was honest when asked about experience with .net, we would've taken a month or two to just explain everything from the start..
But as he didn't and based on his CV (much more experience with .net than me) and 'I understand everything' attitude from the start I assumed he knows WTF was he doing..
Boy was I wrong..
He was also more interested in how much I get payed and if I have a company phone etc..than actually doing his job.. I fucking hate chit chat, and this..well.. he didn't get the hints that this is in no way appropriate to ask.. I've told him that if he has problems with his pay and bonuses that he should talk to the management and not me about this..and that I'm only interested in his actual work and progress..
So yeah, I'll definitely be remembering this guy till the day I die..4 -
Dear Devrant community,
please, tell me that I can report Safari's JavaScript debugger as a bug... Yeah, the whole debugger.
I can't stand anymore on how much it sucks!2 -
Buggered by Xcode AGAIN. The inability of the debugger to do basic debugging relinquishes it to the status of "bugger", relieving it of its "de" title.
Can't show some basic expressions... copied and pasted from the running code
I mean seriously, what do you do if the debugger has more bugs than your project you are trying to analyze?
2 -
I am now the only experienced developer and the person responsible for the delivery of a project AFTER WE ARE ONE MONTH PAST THE DEADLINE! All because user wants to replace the old system with new system with all EXACT SAME FUCKING FEATURES!
-
-Programming my mobile app
-Need to debug something
-App crashes instantly (only) when I try to use debugger.
Guess no more debugging. FML4 -
First time going to college was my first time commiting for real becoming a dev. But with my close minded brain. I believe i only want to became a backend. So here is my story of me getting mad to monitor.
First year i got 24" Monitor. "Shit this is so unproductive, a need a new workspace to place my debugger".
Got another 24" Monitor. "ahh better" -- later on got a Web Developing Class. "Fuck i need moar workspace, i need to see a live reload and a debugger !"
Got a 27" Monitor. "FUCK, there is no way to plug this monitor"
Got No-Brainer-Fast-Bought 1060 3GB. "Finally !". Hmm "this one bigger monitor seems odd, i need to change this to become even"
Got another 2x27" Instead of 1x24" To replace 27". "Why the hell am i wasting money?".
...
...
...Maybe gamble poker when working is nice...
...
...
Got another 27".
12 -
Found this girl who also loves coding like me..... She's very studious... Have been doing projects with her inorder to spent time with her...Like for 3 years now....
But I don't understand what our relationship status is.....I tried asking her out..she just changes the topic every fuckin time... Like she also tend to spend time with me but doing technical stuff only....
I'm totally debugger zonez20 -
How to kill a laptop in two steps:
1. Run React Native metro bundler
2. Run debugger
and a 16GB core i7 laptop on Ubuntu will leave this life :)2 -
Today I found a critical bug to our software and wrote a fix and tested it locally.
Common sense would dictate that especially when it is critical you test said fix on a real release and not with a debugger attached and running onna different device altogether.
I was denied this request because the afflicted machines engineer would not be able to finish the machine before the factory acceptence test.
I stood there with glassed over eyes for a second and then to no avail tried to explain that without this fix he wouldnt even pass the internal acceptance test......12 -
So recently I needed to make a little Tic-tac-toe game with Node.JS for an university project. I previously learned Java and C# so Javascript as a non-compiled, script based language was something new for me.
Now during the programming process I reached the point where I needed to implement a function to change the player who's playing.
I was testing the game and... It seemed like the player was changed twice so it immediately switched back to the previous player.
Using a lot of console.log's I finally stumbled upon the error... (since Javascript or at least Visual Studio Code, I honestly don't know, doesn't have any kind of debugger or something).
Why the fuck does js allow to make allocations in if conditions?
I accidentally wrote one '=' instead of three '==='.
No error, no warning... Nothing.
Since then js and me are not friends anymore.8 -
Okay, I knew one of my colleagues was actually a work freak, but to this point...
He's been working for most of the day yesterday on a school project, and so was I. Satisfied with my progress, I push the code with TODOs on things we had to agree on tomorrow as well as mentioning it in the issue associated with it on Git, with my last commit a bit before 11PM.
I wake up, with a ping on Discord asking me what was that "bug" I just pushed, wondering what editor I use and asking me if I even use the console debugger. Said "bug" was the point of discussion I said we wanted to talk about tomorrow, I replied in the morning. But he decided of the fix on his own and committed it, as well as other things until... 3AM...
Honestly, I don't blame him for choosing at our stead, he's the leader of our branch and the Gitmaster on top of that. I just reproach him to call it a bug, not see the issue, and all that while he could, you know, sleep. And get some rest overall.
This dude has been working himself madly these last weeks, where he did about 80% of what each of the team member was supposed to do in a whole semester (which amounts to 150 hours of work) for this project (we're nine folks on it).
Now I'm pretty sure it's how he works and that he still gets a decent amount of sleep (like I dunno, until 9AM or so), so I don't expect a response beforehand.
And indeed, as he woke up, he replied to me.
At 7:50AM.
8 -
Debugging JS,
*uses chrome devtools*, breakpoints work, everything loads, can work on fixing bug
*uses firefox devtools*, takes more time than IE to show up, the UI doesn't show up, can cry in the corner.
Why is firefox debugger so bad :/6 -
Ice King. Lonely, weird, has a penguin for a debugger and doesn't do as he commands... Yup, that's a Linux guy alright.
2 -
> Am writing code
> Life is good
> Add debugger keyword
> Script pauses
> Type in var name... Undefined.
> ...What?
> Check out local scope. It's there. What the fuck?
> Add console.log(myVariable)
> Refresh
> Logs variable no problem. Cool.
> Type in my var name
> Undefined
FFFUUUUUUU-7 -
Why do I have to "grow" into a managerial role? I like doing what I am doing and would like to do it more. Anyone with some serious advice on how to stay relevant in software development with greying hair and without growing into people management?4
-
Open remote debugger on Chrome but there's a bug on Chrome remote debugger. I can't debug my site because I can't debug a bug on Chrome remote debugger.1
-
Do not use a "debugger".
A debugger is like doing a full-body scan of a sick person. You do not get any specific useful information, and you find a whole lot of information that doesn't help and is just confusing.
Source: Learn Python The Hard Way
Your thought on it?7 -
When a dev leaves a project in the middle, and someone else has to continue their shit, that's the worst fucking thing ever!
3000+ lines of codes in just one class? Fuck!
I don't even know where to put my code, where to put debugger break points, where to... fuck fuck fuck!!! >_<4 -
Ah, the little subtle things we have to iron out as we progress from Junior Developer to Medior Developer.. things like:
- knowing the difference between a carriage return and a line feed (although having worked with analog typewriters helps) and later knowing that Unix-based systems and Windows NT-based systems implement it differently..
- knowing that serialization is important because not all computers interpret data the same way and some computers allocate 4 Bytes for a construct, others 16 Bytes.. and then we get the funkiness of transferring character sets between machines..
- knowing that a whitespace character is not only an actual space (as is known in ASCII as code 32). This one can cause even medior developers a headache, as in: why the fuck does this string function say that "hello I am a duck" and "hello I am a duck" are not the same?! Turns out then in the debugger that when you expand every character in the string you see that string1 contains 32 32 32 32 as usual.. but then string2 contains -96 -96 -96 -96 and you're like.. what the fuck..? Then you know you have to throw \\h regex at it. Haha.
- finalizing our objects and streams (although modern languages do that for us).. otherwise we have to do funky shit like trying to find what's locking a file, which is not so easy to figure out.
- figuring out why something won't work often requires you to not only break down the problem in smaller steps, to use a debugger, but sometimes it's even better to just create a proof of concept, slap some minimal code in there and debug that.. much easier.
- etc.
:)7 -
We've got a new CS teacher this year, and she wants to teach us how to use a step debugger. But, instead of using eclipse or IntelliJ, she thinks we should all use BlueJ, which is just as bad as fucking JCreator! Why do schools, particularly highschools, use these shitty ass IDEs? IntelliJ has a free community version. And I'm pretty sure that Eclipse is just free. Why the fuck aren't we using either of those?!5
-
More adventures in fixing specs.
This particular failing spec is in an included spec helper; I cannot run the spec itself because rubymine is stupid and doesn't know how. Not kidding. I also don't know the codepath it's actually testing because it's fucking convoluted, so I need (rather: want) a debugger to progress. I put breakpoints everywhere I thought it could be, and... nothing.
The stacktrace shows the calling spec in the helper module, a generic `process` method that just calls `super` (from where? who knows!), and a `wrap_every_action` in the ApplicationController. in other words: absolutely nothing helpful. I stepped through the code for most of an hour and didn't get anywhere; just saw lots of rails internals.
ugh,
I'm going to keep bashing my head against this, but what the fuck, why can't you give me something goddamn useful!?5 -
Using the console to print out variables is a perfectly valid method of debugging for new developers: often, it can help you resolve the problem faster than using a debugger.2
-
Just spent the last 6 months searching for why is my left eye blurry. Finally found out today.
If there is a God, could you please make humanity 2.0 a bit more debugger friendy?4 -
MacOs is being a real pain.
I just wanted to do some c programming and I can't get the debugger to work.
Gdb just straight up won't worked because it's not "codesigned" and I've tried to codesign it to no avail.
Lldb fails once I launch the process. This is a real pain man. I just wanted to learn c.14 -
I've been using visual studio for years and always found debugging pretty fun. At my new job I have to use xcode and FUCK DEBUGGING IN THAT ILLEIGBLE SHIT TIER DEBUGGER. and fuck objective-c, at least you can ignore the objective part and just code c..
I never thought I would say this, but damn, I miss Microsoft.10 -
The PS3 has 2 OS types: GameOS (the XMB menu and what you use to play games) and OtherOS (anything else you'd wanna load, usually Linux.) There's a problem with this: There's a build of GDB meant for OtherOS. That's great, but I need some background debugger for GameOS. Why, oh fucking WHY, has no one made a debugger like this? We have the ability to reserve compute units (SPUs) and/or areas of RAM for code to continue running when something else is loaded, why the FUCK isn't there a game debugger???
8 -
Avoid ACPICA if at all possible. It's one garbage tier cluster fuck of bad design, horrible documentation and downright misleading and wrong code
It's meant to consist of an ASL compiler, disassembler, debugger, dumper, various user space utitilies and a kernel resident OSPM implementation *if* you can figure out what belongs to what. Even just compiling this pile of trash is a mystery in itself. Think you need the source files in source/common? EEEEH, wrong. Well, at least partially since most of them seem to be for the user space stuff..? Other ones *are* needed on the other hand. At least the disassembler and/or debugger and/or dumper components seem to reference them. Not that I could figure out how to compile those anyways. The real path to your goal seems to be to ignore a seemingly arbitrary subset of source and header files until your linker stops complaining
There's also a bunch of configuration defines, some of which *you* define, some defined *for* you, based on again others. Of course most of them do stupid shit. Enabling the debugger automatically enables debug logging. Enabling the disassembler force enables debug allocation tracking... What?
The code itself isn't of much help either. Looking in "os_specific/service_layers" you find what looks to be reference implementations of acpica functions in certain os' like windows and unix. Of course I had a look because AcpiOsReadMemory is supposed to read physical memory and I don't know how I would even implement that. But hey, osunixxf.c (xf for interface... of course) should tell me. I'll let you see for yourself in the attached image. Apparently it does fuck all and just returns AE_OK. No error, no logging, no nothing. Just ok. As you can imagine, AcpiOsWriteMemory doesn't do much more either.
...okay so maybe physical memory accesses aren't actually used and these functions are some sort of relic from past times? Nope! They are absolutely necessary for doing low level device interaction. WTF. So finally I went to the linux source and checked how *they* implemented them, and just as I thought, these functions are anything but no-ops...
...So for what fucking reason do these stupid interface implementations even exist but to purposefully mislead you?? They aren't used for fucking anything! As far as I know Windows doesn't even *use* ACPICA and Linux have their own fork with working implementations... They just sit there, just to tell you how to NOT do it
So that's some of my thoughts about ACPICA. Note that I haven't even used it as a library yet, I just got it to compile and link and it already fucked with me this much.
There's also so much more I didn't mention like that you *have* to modify the acpica source in order to get your own platform header working (else #error) eventhough the docs explicitely instruct you not too but you get the point
Don't use ACPICA if you don't have to. Save your sanity for something that's worth it
-
Spent hours troubleshooting an internal app that had zero logging today. It would just terminate, no exceptions, no feedback to the debugger, NOTHING.
Turned out to be the damn corporate virus scanner blocking "malicious" behaviour. Good thing my desk is so heavy or I woulda flipped it... -
First time me ranting about PHP.
First time. I still really like the language.
But what the fuck.
I am debugging, I narrowed down bug to my validator.
I played with php console and debugger and narrowed down to that one offending line.
Narrowing down to smaller and smaller examples when it dosent work, confusion and tension grows in me.
And then it hit me.
Confusion got to apogeum.
Anyone, if you know the anwser, please tell me.
WHAT THE FUCK?
maybe thats task for stack overflow? Hrm...
No, I dont have time to explicitly tell what I tried to google and spend 4 hours to have all checkmarks ticked before asking lol
39 -
Fed up with f@_#-$&@_ Microsoft bullshit, computer refused to install IIS without a reboot first. Rebooted, got bluescreen with some error like APC_Index mismatch since it was hooked up to an external monitor (this has happened before, but only when booting into Windows, not Ubuntu), god knows why now since it was hooked up to same monitor before reboot and worked just fine. All this because some stupid school related task requires Visual Studio and a web project-solution that takes ages to run/debug which I would rather build and devug through attaching remote debugger to the running IIS-process. Instead I get into a boot-loop when the screen is connected, and when I connect the screen after a normal boot it restarts itself. Why is it always like this? Most of the time is spent just to setup the environment or making Windows work. F#&#_ this and the assignment, goodnight.1
-
I regret moving to backend. I loved the days when I used to write lines of code and refresh my browser for the changes to be displayed on the screen. I loved seeing the output of my code, the code flow, the light weight text editor, the visual satisfaction and the chrome debugger.
Now I am fucked up, I am working on creating microservices for restful api. I am hating everything about it. The fact that I should compile the entire war, manually copy them to a webapp folder, restart my tomcat and wait for 5 minutes just to see my code, and the text editors are just a pain in the ass, the debugger sucks too.
I was so looking forward to being a backend Dev because I thought Java was cool and I also was fedup with cross browser optimizations on the front end. Now I would gladly write a streaming service foe ie6. Spring has fucked me up so hard
God save me from this mess.6 -
Stop commenting out code blocks!
Either fix your shit or delete it.
I am open to argue what fixing may mean, as it is perfectly fine to make your broken code not reachable, e.g. via feature flags or skipping certain tests. Yet never ever should you comment those blocks!
So you say you want to keep it for historic reasons? You know, that is why we use version control! If you ever need certain functionality back, you can restore that state.
Each decent IDE also offers a local history where you can even restore code blocks that weren't even pushed or committed. So use that!
Commenting out test cases is a really bad habit, as you have no reminder that you shall restore it.
And no, a TODO and a FIXME won't count as a reminder as you have to actively look for them. And we all know how well that goes, don't we? (One time, I found a typo of a `TDO`. So even with a regular lookup for TODO, stuff will slip.)
Each test suite offers you ways to skip tests if there are valid reasons why they should not fail the build temporary and they offer colorful feedback. Yes, that means that your tests won't be green, but guess what: That's a feature! They shouldn't be.
That yellow is a fine reminder, aka warning!, that you should really fix your shit.
Commented code screams: "I DON'T KNOW WHAT I WAS DOING!" and it confuses the hell out of other developers ("Was this commented because of debugging purposes and should be active again or can I safely delete this!?") and adds verbose crap to the code base.
If you find yourself to be in a place that you comment code a lot, I also argue that your workflow is broken.
When you are using a decent debugger, there shouldn't that much of a need to comment in and out a lot of code in order to reason about your code-base.4 -
Stupid stupid university custom exam IDE... first thing select a few lines hit tab oops replaces code with tab character... compile is alt+C and run is alt+R (never seen that before) and you have to go save -> compile -> run.. instead of just hitting run and last but not least it syncs your code with the server so every save file takes 3-5s at which time the editor freezes
ALSO NO DEBUGGER OR JAVA CONSOLE...6 -
Unpopular opinion: Firefox is a better web debugger/ development tool than Google Chrome... so many functionalities packed in that sweet gem.11
-
I was using Delphi 7 to develop a desktop application in Windows 2000. Every time my application opened the standard Windows open file dialog, I'd get a BSOD but only if I was running the application with debugger attached. Never found out WTF was wrong... Just changed my code not to show the open dialog if IsDebuggerPresent() was True.
-
Don't you just love how you have to clone the whole 40GB library's repo, load it in your IDE and hook that IDE's debugger to your app, because some moron developing that turd decided to mute an exception?
Thanks God the lib is opensource. Otherwise I'd have to jdb without any sources, which sounds like a lot of days of a lot of fun (y) -
@apple since I can't move Xcode's instruction pointer without crashing Xcode or my app, I have to use a global with 'if' statements to have optional debugging logic.
if( ! gAppleFuckTards) {
... do optional code stuff
}
and then change the value of gAppleFuckTards with the debugger to execute the code.. but WAIT
Xcode purports to be able to change values via debugger but really cannot... can't change gAppleFuckTards to false in the debugger. But that kinda makes sense as it is an empirical truth.
Thwarted by the cosmos again!2 -
Programming for iOS is pure pain.
Programming with ionic on a Safari debugger is still worse. It's a crime against humankind.
I regret the IE 6 debugger. Yes, I know what I'm saying -
Coding chalenge.
So... Spent almost two hours to put this little device to work with the keypad.
The device is a arduino micro, special one that can work as mouse /keyboard or any kind of input on most devices (pc, Android phone,...)
The objective is to make a macro keypad to:
- Fast insert text
- Play sounds in games over voice chat.
Think of it like this, you start a new html file, press one key and all the base code is inserted.
So... Why so long? Tought was the hardware, tought the keypad could be set differently that most, code mistakes...
My error was all here, masked from the debugger by a if:
char keys[ROWS][COLS] = {
{'1','2','3','4'},
{'5','6','7','8'},
{'9','10','11','12'},
{'13','14','15','16'}
};
Easy to figure right? Only saw it after reading all the code twice.
9 -
This rant is about myself and anyone whos like me: using logs over a debugger
So, sometimes when I wanna quick check something or make sure, if and when something get's executed or I've ran into a Problem, I add a few log/print statements to check in console.
But I don't think about proper and helpful messages, since they aren't supposed to stay in code. So I often type what comes in my mind, like memes or song lyrics.
The last time this became a huge act, was Code review/ Prototype demonstration with Clients (which I didn't knew about, otherwise I would have removed them, I swear) and Boss and my Code printed "show bob and va...", "send nudes" and stuff... in loop... to stdout2 -
Seriously, I get a smaller hart attack if there is NO errors shown in the debugger. I wait about 5 seconds before I breathe against be sure it is correct.
-
Wow. This piece of bullshit runs completely flawlessly in the debugger, but throws exceptions like fuck when running it normally. How am I even supposed to find that fucker of a bug?3
-
All I am asking for is a debugger in Xcode that works as well as Macintosh Programmer's Workshop ( MPW) circa 80's/90's. Maybe I am being unreasonable?
I stepped a line in the debugger and all the variables disappear... and all I get is the spinny "fuck you" indicator and the variables all disappear.
But here is the worst part... Apple isn't holding any of those fucktards on the Xcode team accountable for producing a shit product.
I'm really glad I don't have to do this as a full time job anymore. Then why do I continue to pound nails with my forehead (use Xcode)?
Whip me, beat me, make me use Xcode...
5 -
I decided to learn Flutter, because the idea of a common code base between Android and iOS sounds nice. I'm late to the party, I know.
So I install everything and start typing in the tutorial. TAB... two spaces. I absolutely hate that so let's change it. In the settings, it sends me to a FAQ which more or less says this is the way it is, deal with it. But I want my tabs to be four spaces, every code editor since the dawn of time could do this... I'M PAYING FOR THIS SHIT!!!!!!!
Ok, let's check the JetBrains website, I'm starting to lose my patience, but let's do it. At this point I should also mention that I'm feeling pretty stupid. I mean, I'm checking on the internet about how to do something which obviously must be obvious, why am I not seeing it?
I find a page on the official website. JetBrains' replies are along the lines of "Why would you want that?", "The holly wars between tabs and spaces are over", "Most people like it this way", "The overlords said this is the coding style to be used" (Ok, the last one was me reading between the lines). At the end of the thread, they provide a "hackish solution" (their words, not mine). Which doesn't work. Because why should it?
Not even when PyCharm's debugger randomly shat itself and I had to use print statements I got so angry. That was relatively fine, bugs are a fact of life, and the overall package is good, so I kept paying.
But now you're telling me that I cannot use what should be a common feature of every code editor just because you and the overlords know better?
Well, fuck you and the horse you came in on JetBrains, you've just lost a customer.17 -
disclaimer i dont understand css to begin with so you can discard my opinion
You have all these options for width https://developer.mozilla.org/en-US... , but guess what none of them do anything different as you brute force try them all in the chrome debugger. Dunno what cascades except my butthurt
so fuck it ~1000% width works and has an ugly overhang, but fuck front end9 -
I don't care how magic your framework is or how good your "developer experience story" is, if I can't attach a debugger to my own code then I can only assume that the problem is your shitty code.2
-
I feel like an imposter sometimes but then I look at some of my colleagues. I'm not really sure whether that's a good thing or not.1
-
Debugging WebRTC is pure hell.
For starters, it's JavaScript, so you know this isn't gonna end well. Second, it's still in kinda beta phase for some browsers so you gotta add polyfills. Let's talk compatibility now. During normal days, yeah, I could ask for a couple of computers in the office, each using a different browser. But, covid. One browser mishbehaves and doesn't wanna share the camera with the other browser, so I can't really test a connection with the only 1 computer I have. I can't take my partner's computer all day to debug.
Solution: ask the marketing department or even the execs to video chat with you to test it on a staging server. So I push my changes to the server, wait for them to build, call my lab rat, check all the bugs, clean the code, push the changes back up. No fancy breakpoints. I'm doing the old style like my great uncle did. Oh wait no, he was pretty intelligent, but my lab rat isn't. They probably don't know what a console is. So no baby I'm not only talking about console logging the problems, I'm talking `alert` the heck out of the bugs - okay no, I'll just display the objects in the middle of the screen. The screen is my console.1 -
Well, this one was very satisfying.
When I resigned from my previous job, there was this one last task I had to finish. The task was to implement an identity and access management system that would work across three different platforms they had. I used to work on one of them which had nothing of the sort but the other two had something of their own. Here lies the kicker, it had to work with existing authorization system in other two platforms. After explaining multiple times why that is a bad idea, I gave up. I created an interface, no implementation, documented how the interface was meant to be used and got the hell out of there. -
I am learning exploit development on Windows and I have a problem with it, when I analyze the registers ESP and EIP.
I am able to overwrite both ESP and EIP.
The problem is that I can not make use of "mona.py". "Mona.py" keeps showing me that there are no pointers and any os dlls whereas that is not true.
Immunity Debugger is working completely fine.
I need "mona.py" to find pointers to ESP, but it says there is none.4 -
Whenever anyone asks me why I dislike C++ I'm just going to point to this current app I'm working. Had a unit test with an extern method declaration that had 7 or 8 different parameters. No big. Problem is that the ACTUAL definition of the method had 1 less parameter than the extern declaration. It worked perfectly fine in x86. Ported to x64, compiled fine, hard crash at runtime. Debugger not a super lot of help. Took me a couple days to figure that one out. Also I am broke so I can't even drink the pain away. Neat.
-
Stop teaching T-SQL on paper. If i have to write one more transactionsafe sql query without a debugger i'm going to fucking kill somebody.
-
Apparently if your og:img meta tag has "Default.png", you'll break facebook's share API...
Cool, cool.. I ain't even mad.7 -
Am I the only one who uses the breakpoint feature in PHPStorm for highlighting parts of code instead of actually debugging?8
-
One of my trainees some years ago was too lazy to process his networking homework, so he just modified the binary of that cisco tool he would have to use and removed the password prompt at all to access the solutions.1
-
Editor, interpreter and debugger of sorts for esolang Piet
https://dustincompetent.com/piet
There's lots of room for improvement but it was fun to implement2 -
Had to track down IDA 5.0 today because I need to decompile a DOS program and DOS' included debugger wasn't cutting it. (Related note: If anyone has a copy of SOURCER, mind sharing?)2
-
Just got myself a Pixelbook and man is this thing a sweet little machine! Excellent battery life, a pretty decent backlit keyboard and I can work on my personal project using VSCode and the integrated debugger!
Google is doing a good job with making Chromebooks developer friendly.2 -
Whiteboard 😂
But seriously Jetbrains I am IntelliJ ultimate user for 6 years or something - I like their debugger expression watch and multiline expression evaluation.
Also like their git integration, the fact that you can only mark some lines in file to commit.
I am used to their keyboard shortcuts.
I like there is vscode cause it made my IntelliJ work better.
Competition is always good.
Maybe I switch to vscode but only if I’m broke and can’t afford IntelliJ. -
To all the masochists who spent hours debugging misspellings:
1. Learn your tools
2. Learn good practice
Every IDE should point out when you're not using a variable you've initiated or using an uninitiated variable as well as at least highlight, if not simply list, every occurrence of the variable under your cursor and let you find all references or even display the number of references next to a variable at all times, and finally, every IDE should autocomplete for you so when it doesn't you know you've messed up. Good IDE makes all the easy mistakes hard and all of the hard tasks easy. Including running tests. If you don't know how to configure your IDE to do all these things take time and learn it. If you still can't figure it out, replace your IDE maybe...?
Also use the debugger. Preferably one that nicely integrates with your IDE. If you don't, check point 1.
Also write tests and *run them*.
Also if your misspellings tend to consist of a missing `s` at the end of a plural noun just call it `entityCollection` instead of `entities`. And read up on more good programming practices and naming conventions.7 -
>Working on code
>Shit works as intended first try, nice
>Goes to play strange bootleg Gameboy Color ROM sent by a friend
>ROM immediately fucking dies
wtf.svg
>Pop emulator's debugger
we're executing from VRAM, stack's firmly embedded in ROM
>why
>Add execution breakpoint to entrypoint of game, restart emulated system (because i'm actually using the legit bios i hacked so it allows null/corrupted games to run)
>Step through everything, everything goes well until all of a sudden we call a function and shit hits the goddamn fan
well we have the culprit
>step through subroutine
if <unused_byte_in_HRAM> != 0 then stackPointer+=32;tryAgain();else return
>***y***
>Realize this is using a bootleg Memory Bank Controller with hard-backed encryption so none of the bytes executed or read as data are the right byte
>Find emulator that'll handle the jank MBC
>read code to try and figure out how it works
if checksumExtendedLogoBlob == some_number then set MBC_Bootleg1 else if checksumExtendedLogoBlob == some_other_number then set MBC_Bootleg2 else if...
>of course
>Spend 10 minutes finding the right bootleg MBC
>code shows 8 possible tables for real bit order based on some value in the cart header
>look for code that gets this value
>not in the header
>not in ANY header in this 1000+ file emulator
>not in any related cpp files???
>get desperate
>email author
>"Delivery failed: email doesn't exist"
fuck me i guess2 -
Programming has taught me
1. Importance of patience, friends and family and yeh StackOverflow too...
2. Importance of small contributions towards dev community.
3. How smaller things can make big changes.
4. Helping others and getting help if you get stuck.
5. Anyone can code, but very few can build robust solutions. Project not just coding but it needs preparation and planning too.
6. Importance of reading documentations, writing test cases, debugger programs.
7. You can learn things even if you have no idea about it. It just takes your interest. -
Talking about the Open Graph protocol (http://ogp.me/)
Why the fuck does the Facebook Object Debugger tell me that my image in the og:image meta tag could not be loaded when I put a HTTPS link in there, but when there is a HTTP link with a permanent redirect to the HTTPS link it can load the fucking image.2 -
This was true with the ancient IBM 6150/6151!
When you looked at the registers of the CPU with their debugger, all uninitialized registers had the hexcode 0xdeadbeef!1 -
O.M.F.G how much longer is that gonna take?!?! It's been 2 days already! 2 fucking days!!!
That's it. Fuck the docs. I'm going hardcore now: hooking up a debugger and diving into the unseen depths of Spring's automatic JPA repo initialization.
Unless any one of you knows how to
1. Manually create jpa repo interface bean
2. Make transactions work [also enable them manually by declaring beans in @Configuration]
and do all this in a single @Bean method. Jpa provider - hibernate.
Nobody? Not a single one? Allright then, I'm going in :(1 -
!rant
Every type of doctor is a different kind of debugger for the Human Operating System 🤔
They debug system services like "ear", "throat" and "poop".
Sometimes they even repair or take apart systems for different reasons!1 -
Fuck you Firefox and your shitty debugger.
Why do you try to be so different, to the point where you make the error messages obscure?
Google the error message I get in the Chrome debugger - hundreds of results.
Google the error message I get in the Firefox debugger - I can count the results with my fingers.
Just use the same error messages god damn it.
P.S: Also, why is there no fucking option to open an image in a new tab, like in Chrome?1 -
Google acquired two interesting products companies last week.
One is making customizable phone apps from spreadsheets the other is gathering sales data from local shops.
appsheet and pointy
At this point I think they’re still missing code editor. Microsoft have visual studio and amazon as always was first and acquired c9.io when vscode was one year old.
How the fuck they missed the code that would run remotely on multiple machines should have ability to connect to one node with debugger after they fucked docker with their k8s.6 -
OK, I know the general consensus of StackOverflow on DevRant...but jesus h christ...do devs not debug their own shit anymore? I can't say how many times I see "I get this exception...how do I fix...hurrr durrr....". When it all comes down to it, if they just attached a debugger and looked that variables/properties, they'd see what kind of stupid shit they are doing.
-
Ranted earlier about how my debugger was fucking up. Jokes on me, it's now the only thing that works well.
The fucking C++ code behaves normally in debug build, but when in release build throws a SEGFAULT out of nowhere. Bet it's tellg() or my unsigned to signed conversion that fuck things up (while they work perfectly in debug, I repeat). But I can't tell, since the only way I have to trace back the issue is the disassembly ¯\_(ツ)_/¯7 -
Don't attempt to debug a crash on startup using visual studio remote debugger over team viewer vpn using the worlds worst German hotel internet connection.
If you do, get a drink while it takes 2 minutes for the debugger to break. -
Not much tops the orgasm from powering thru 500+ lines of code in the zone... in vim...no debugger.. and without compiling just visually seeing in your mind the assembly be generated... and code being stepped thru.. and then compile and test and everything works as expected.. not sure anything tops that feeling ... definitely have to be in the zone.. one distraction and boom gotta compile to make sure nothing broke3
-
You know something has gone wrong terribly when no MS Office program or Adobe reader starts while the debugger is waiting at a breakpoint.
I'm really curious which part of the kernel or system near userspace-components can cause such behaviour and where MS created pointless tunnels between independet software to let that happen. But I think I will never find out. -
"Out of process VS debugger to enable the VS debugger to use a 64 bit process - resolving many out of memory performance and reliability issues."
Someone pinch me!
https://docs.microsoft.com/en-us/...1 -
I cannot for the life of me get the debugger working in RubyMine because debase gem wont install. WHY AM I WASTING TIME DEBUGGING THE DEBUGGER INSTALLATION?1
-
Isn't it fun when you are given a library or framework and that in order to debug it you have to use some hacky way of hooking the code to a special instance of the project?
Even more fun: the developers by default don't debug the project with tools, but rather with logic. Ok, that's a good way to debug but it shouldn't be the only way to debug. I don't want to go back to the age of coding on paper. At least give me a stacktrace that's halfway clear on what's happening there. Even worse is when the framework doesn't document its own problems! stacktrace.someMagicalMethodNoOneKnowsWhatItDoes(). Having to read the even more mystic and overly verbose documentation! You're just left there trying and guessing shit, even for the senior devs!
And do you know what's more fucked up?! Fucking using println() to debug!! And they take this shit seriously! I don't understand how these people call themselves programmers. No breakpoints? What the fuck, man!
Just give me Visual Studio for fuck's sake. I don't want to code in a broken IDE with a broken framework. Development on its own is already hard enough, so don't make it harder by giving me crappy frameworks and crappy IDE's that only work half the time.
Debugging without a debugger, with broken IDE's, with broken frameworks, I'm sorry but that's just not for me. And then the framework dares advertise that it 'lets the developer focus on business code!' (how many times have you heard this crap before?). Right, the only thing I focus on constantly is trying to figure out why their broken framework doesn't work.
Arghhh. -
So I'm gonna finish my interpreter. No matter how much fucking work it is to implement a proper cross platform terminal library, because all the existing ones suck. I'm gonna write a debugger for it.
And then I'm gonna learn to play the ukulele.
And I'm going to start a new project that may actually make me a good sum of money.
This is the plan. If I don't do this then literally fuck my life, I might aswell jump off a bridge because I can't fucking do anything12 -
Xcode: took away the ability to manage multiple windows as documents; everything is a half-assed safari browser window that neither works like Mail nor like Safari.
Xcode: took away the ability to have variables in the debugger in separate displays, now it is a single basket of eye-bleeding variable/data spew.
Xcode: took away the ability to modify variable values in the debugger, it's just broken and lets you think you can but reverts the value.
Xcode: took away the debugger's ability to modify the execution pointer. You can't move the current line of execution to the previous line, the line past the current line, nothing.
The same internal human virus that manages the Alzheimers 'upgrades' of macOS Server seems to be managing the Xcode debugger, more aptly named now "Xcode stepper" cuz it makes a lot of motion but goes nowhere fast.1 -
Visual Studio and its compatibility with Linux applications.
I don't know if I'm the only one, but this is my setup:
- Visual Studio 2017 on Windows 10
- Ubuntu 18.04 subsystem on Windows
I just can't do any Linux coding in Visual Studio... it is using my subsystem as a Remote Compiler and debugger, and a simple Hello World program does build and run successfully, but EVERY SINGLE LINE HAS ERRORS! It can't find stdio.h! Not a single include file works! They get auto-completed so it knows where the files are, but apparently opening them to see all the methods is too much for Visual Studio! I'd say the problem has something to do with IntelliSense since only inside the IDE my code has errors, compiling (which happens on the subsystem) works like a charm.2 -
I regret ever picking my CS major every time I stare at my VS Debugger and am stuck reading the values stored in a List<Int>. Why, List<Int>, as the backing for my shortest path, do you not have the proper values after I walk my tree.
I have lovingly set up my Priority Queue. I have followed the class notes and lectures.
Oh why, my List, have your forsaken me?
Oh.
It's a recursion bug. I'm not updating nodes properly.
I'm a dumb ass.2 -
I'm currently trying out Apache Cordova. Feels like playing minesweeper for the first time.
But as always a debugger rushes to rescue me:
Ripple :: Environment Warming Up (Tea. Earl Grey. Hot.)
Yes, I'm gonna make me a cup of tea now.1 -
(I'm not completely sure of what I'm saying here, so don't take this too seriously)
Settling on a language to write the api for ranterix is hard.
I'm finding a lot of things about elixir to be insanely good for a stable api.
But I'm having a lot of gripes with the most important elixir web framework, phoenix.
Take a look at this piece of code from the phoenix docs:
defmodule Hello.Repo.Migrations.CreateUsers do
use Ecto.Migration
def change do
create table(:users) do
add :name, :string
add :email, :string add :bio, :string
add :number_of_pets, :integer
timestamps()
end
end
end
Jesus christ, I hate this shit.
Wtf are create, add and timestamps. Add is somehow valid inside the create, how the fuck is that considered good code? What happens if you call timestamps twice? It's all obscure "trust me, it works" code.
It appears to be written by a child.
js may have a million problems. But one thing I like about CJS (require) or ESM (import) is that there's nothing unexplained. You know where the fuck most things come from.
You default export an eatShit() function on one file and import it from another, and what do you get?
The goddamn actual eatShit function.
require is a function the same way toString is a function and it returns whatever the fuck you had exported in the target file.
Meanwhile some dynamic langs are like "oh, I'll just export only some lang construct that i expect you to specify and put that shit in fucking global of the importing file".
Js is about the fucking freedom. It won't decide for you what things will files export, you can export whatever the fuck you want, strings, functions, classes, objects or even nothing at all, thanks to module.exports object or export statement.
And in js, you can spy on anything external, for example with (...args) => debugger; fnToSpyOn(...args)
You can spoof console.log this way to see what the fuck is calling it (note: monkey patching for debugging = GOOD, for actual programming = DOGSHIT)
To be fair though, that is possible because of being a dynamic lang and elixir is kind of a hybrid typed lang, fair enough.
But here's where i drop the shit.
Phoenix takes it one step further by following the braindead ruby style of code and pretty DSLs.
I fucking hate DSLs, I fucking hate abstraction addiction.
Get this, we're not writing fucking poetry here. We're writing programs for machines for them to execute.
Machines are not humans with emotions or creativity, nor feel.
We need some level of abstraction to save time understanding source code, sure.
But there has to be a balance. Languages can be ergonomic for humans, but they also need to be ergonomic for algorithms and machines.
Some of the people that write "beautiful" "zen" code are the folks that think that everyone who doesn't push the pretty code agenda is a code elitist that doesn't want "normal" people to get into programming.
Programming is hard, man, there's no fucking way around it.
Sometimes operating system or even hardware details bleed into code.
DSLs are one easy way to make code really really easy to understand, but also make it really fucking hard to debug or to lose "programming meaning".7 -
Magento Debugging Horror!
Changing lots of things in magento with no problem. Continuing development for quite sometime. Suddenly decide to clear cache to see affect of a change on a template in frontent. Suddenly magento crashes! There's no error message. No exception log. No log in any file anywhere on the disk. All that happens is that magento suddenly returns you to the home page!
Reverting all the changes to the template. Clear the cache. Nope! Still the same! Why? Because the problem has happened somewhere in your code. Magento just didn't face it, because it was using an older version of your code. How? Because magento 2 even caches code! Not the php opcache. Don't get me wrong. It has it's own cache for code, in a folder called generated. Now that you cleared all the caches including this folder, you just realized that, somewhere something is wrong. But there is no way for you to know where as there is absolutely no exception logged anywhere!
So you debug the code, from index.php, down to the deepest levels of hell. In a normal php code, once the exception happens, you should see the control jumps to an exception handler, there, you can see the exception object and its call stack in your debugger. But that's not the case with magento.
Your debugger suddenly jumps to a function named:
write_close();
That's all. No exception object. No call stack. No way to figure out why it failed. So you decide to debug into each and every step to figure out where it crashes. The way magento renders response to each request is that, it calls a plugin, which calls a plugin loop, which calls another plugin, which calls a list of plugins, which calls a plugin loop, which calls another plugin.....
And if in each step, just by accident, instead of step through, you use the step over command of your debugger, the crash happens suddenly and you end up with the same freaking write_close() function with no idea what went wrong and where the error happened! You spend a whole day, to figure out, that this is actually a bug in core of magento, they simply introduced after your recent update of magento core to the latest STABLE version!!! It was not your mistake. They ruined their own code for the thousandth of time. You just didn't notice it, because as I said, you didn't clear the `generated` folder, therefore using an older version of everything!
Now that after spending 7 hours figuring out what has failed with absolutely no standard way of debugging and within a spaghetti of GOTO commands (Magento calls them plugin), why not report it to github? So you report it with a pull request. This also takes 1 hour of your time. Just to next day get informed that your pull request is rejected because another person already fixed the bug and made the same pull request. It was just not on the latest stable version yet!
So you decide to avoid updating magento as much as possible. Because you know that the next Stable version will make your life and career unstable. But then the customer complains that the Admin Panel is warning him of using old Magento version which might pose SECURITY THREATS! -
Looking for a suggestion here. I am looking to introduce my wife's niece to the "art of computer science". I am looking for something basic yet fun. So far, my plan is to help her design her own website with a blog.13
-
Shame on you Facebook Developers!
I’m neither messy or anal coder, but whenever I push something to production I make sure to handle all debugger warnings... I don’t think it’s perfectionism, rather good practice, makes important bugs easier to find. ;)
A single Facebook SDK Framework has 70+ unhandled warnings, trivial things, could be fixed in a half day...
I had to use ‘inhibit_all_warnings!’ flag literally for the first time, not to get frustrated every time it gets updated :/
P.S Not to mention I had to change the dependency manager because (with the newest update) they have written themselves out of compatibility with the one I was using... C’mon guys. Not cool. -
LPT you can just write debug(foo) and it'll break as soon as chromium debugger hits a foo function call. Undoable by using undebug(foo).2
-
I hate so much when i write a lot of number of lines in my code and when i start the debugger there are a lot of errors...... I Forget to initialize a variable 😑
-
PIC C programming on Linux with MPLAB, the editor from the manufacturer
I particularly hated the debugger
I don know of it was just me because I didn't understand it but *screams* SHIT FUCK WHY DON'T YOU READ THE DATA YOU FUCKING CRYSTAL TRICKED INTO THINKING!? -
How are you supposed to read and understand 1000s of lines of uncommented, undocumented apex code and then make changes to it and do it all in time? Salesforce doesn't even provide a free debugger.
-
So I'm not much for Linux, but I'll admit. It's a pretty damn solid environment, especially for programmers.
Since my main computer can't afford to have Linux on it, I decided to start working on making the Raspberry Pi handheld notebook. But after I added up the price for all of the components, it's almost three hundred dollars.
Personally, I would love to have a mini computer everywhere I go. A Chromebook is ok. But I guess you need to take into consideration that it is NOT ment for programming. I have found several IDE's and found none of them have a debugger or a way to execute my code.
I did some thinking and I'm starting to wonder if it is worth it.
It's a hand held computer with ubuntu on it. What's the worse that can happen? I don't solder the battery correctly and the whole thing explodes in my hands? Yeah that's pretty likely. Another reason I look at getting it is because there is so much fucking theft at my school it's hard to believe we don't have armed gunmen at every corner since everyone is always sober or high as shit.
Having an 11.6 inch Chromebook also puts me at risk of getting mugged, because who the fuck wouldn't want to try and pawn a laptop for drug money? At least with a handheld I could keep it in my pocket where I know it'll be safe.
What do you guys think?
Should I build this little thing or keep my current Chromebook but try to keep it safe?4 -
Side job - some consulting.
Second day of editing 70k one file, unmanageable javascript code to find memory leaks for some embedded device that is running on chromium embedded framework. Luckily there is chromium remote debugger for it so I can make snapshot and place some breakpoints.2 -
Here developing a react native app using console.log everywhere cause the debugger won't stop at the right line or skip libraries when stepping.
But I still somewhat like RN 💙 I think it's a fairly ok framework when you get the hang of it.
I was thinking about giving Flutter a try though, and see how easy it is to use. What do you think about this library?2 -
This little cute RoboHon could be the perfect debugger replacing the rubber duck!
Source: https://theverge.com/2016/4/...
1 -
Phpref tricked me into thinking my variable has no whitespaces in it. Damn. Fix your CSS please :D Debug the debugger :D
1 -
Programming embedded systems from scratch. All hardware, memory, timers, peripherals, etc, must be set up correctly at startup, and if you set even one single bit incorrect in any of the sometimes hundreds of 32- or 64-bit configuration registers, you are screwed. There is often no terminal that prints error messages to help you, but if you are lucky you have an (often very expensive) hardware in-circuit debugger to step through the start up code.2
-
Sometimes I feel like going back in time and changing some things. If life would have a debugger would know when I am doing a mistake.3
-
When your boss asks you to debug a simple 404 error for an image. The VP of my department doesnt know how to use debugger tools lol1
-
Coworker was on cppcon (hope it's the name) and apparently Visual Studio debugger is gonna have "step back" ability !
Holy proper shit, I'd love to be among the engineers behind this, awesome1 -
For those with hiring experience, or just informed opinions.
Candidate A:
1.5 years self-taught web development, primarily Javascript, but also Ruby & Golang
6 months commercial front end experience
Brucey Bonus: a significant fullstack personal project (deployed), plus lots of smaller projects. Has focused a lot on learning OOP and functional paradigm principles.
Candidate B:
As candidate A, but instead of a personal project, has made a couple dozen PRs on a big open source project (ie Mozilla’s debugger). They seem to have eschewed really dialling down into algorithms/paradigms, preferring to learn “in the wild”.
They both perform equally well in interview tests, and appear to be engaging, hardworking and approachable.
Which one do you pick, and why?25 -
#define someError ( -1)
int func(params *param)
{
//some code
if(condition)
{
someError ;
}
}
Spent like half and hour on debugger thinking why the fuck does it skip my statement. My manager who was passing by saw me puzzled and asked if he could help, so we spent another 10 minutes without success(tho my manager is technical guy but he had an unlucky moment I guess). Eventually senior manager saw our wtf faces and asked what is going on, it took one question for me to light the bulb "someError is a macro right?"
I guess you can imagine my embarrassment at that moment..
PS: Forgot return keyword before the error code. -
Today I discovered trial and error driven development for myself:
Me, reading spec..
Spec: „Do something with an CSR“ (not the exact wording :D)
So instead of just googling C# + CSR and copying the code examples,
I went like:
What means CSR -> Certificate (Something Something)
-> could be this namespace (Something with „Crypto...“ in its name)
-> could be this class (Something with „Certificate“ in its name)
-> take the easiest overload (string is always nice)
-> try filling in the parameters from the spec
-> start debugger and inspect properties
-> repeat if necessary
I don’t know if this is the correct pattern to proceed my project with...
But hey, today it worked and now I also know, what „distinguished“ means -
Sadly took me a little longer than I’d like to admit to go from well placed print statements to using a debugger. Granted there are times when print statements are needed, but for all the devs out there who are using an IDE with a perfectly good debugger and yet doesn’t use it... please use it. It literally gives you a mapping of all objects and data types around a break point that you can easily glance at to speed up debugging. Go figure!9
-
sweaty_decision_meme.jpg
- Debugging some application locally (with debugger)
- 20-30 manual step-ins, tracking those values VERY closely
- debugger becomes a little sluggish
- move mouse to select a line to jump to
- cursor is lagging: all jumpy and everything
- CTRL+ALT+F1
- everything freezes.
sooo...either reboot the laptop and lose all the work, or wait for OOMK to kick in, which could be hours, depending on the level of memory starvation.13 -
I can't connect the fucking safari debugger to the fucking iPad.
It opens the window and closes it after a few seconds, or sometimes (1 time out of 20) it just works, without no fucking reason.
And you should wonder "why are you asking for help here, that's not the fucking StackOverflow" the problem is that I don't know where else to ask. The next step will be resurrect Steve Jobs and just ask him why9 -
Part of one of the workarounds for Dirty COW is to disable ptrace.
ptrace is generally needed by debuggers.
I am team lead for L2 support at a company which makes a debugger.
RedHat are now shipping this workaround.
*ducks for cover*2 -
debugger; // JavaScript
It's a statement not a function, but it can save lives when console.log debugging fails. -
YES, take that chrome debugger extension i got you to show my page! I have errors, hell yeah i can deal with i didn't include js files!
-
Whenever there's an annoying bug that refuses to go no matter what I do, I just go to sleep. Sleep is the best debugger.
-
Spent 3 weeks getting brainf#@ked by c++ templates and SFINAE trying to "compile-in" the conditions. Later got to know performance was not required this time. FML!
-
Sublime text... works on almost every OS.
On my side projects, probably visual studio (i really like VS debugger).
Sometimes vim, if there is no GUI to work with2 -
When did people decide that developing using a tech that doesn't even have a proper command line debugger is a safe bet for a production system?
NodeJS, tower of nonsense... -
For me, biggest influence have been my bosses.
One of them mailed me that my work was shit and he was cutting my pay while I was far off with my father post surgery and battling a terminal illness.
The other one gave me an offer while I fired my previous boss from the job of being my boss. He also knew the exact reason for my switch. That taught me a lot on what kind of person/programmer I want to be. -
Debugger still throw an exception, you looking for a bug for hours . Couple hours later someone remands you that CSV is comma-separated but your file has semicolon!!! Wwrrrrr
When I working too long I make noobs mistakes.1 -
I thought debugging node.js would be me throwing a bunch of commands at terminal but thankfully saner minds created vs code debugger.
Also vs code documentation should be a lesson to everyone on how to document stuff. -
Why the flying fuck does a resultset get returned with the pointer going to BEFORE the first fucking entry? And why does the error say "no data available"????
I saw the stinking values in the debugger, you fat cunt, don't tell me there is nothing there.
But hey, at least now my boss doesn't have any expectations whatsoever. I sure am dense motherfucker.1 -
Not too long ago I bought 3 monitors. Now I have my IDE on the center, console and debugger (and devrant) on the left, git and music on the right. Still figuring out the best arrangement for all windows but this already feels awesome!3
-
Amstrad CPC 128 book(GWBasic), my first lines of code about a loop game (Thousand of lines without debugger or memory save!) So it was like woot after 3 hours writing to see running the endless ship gamming trying to avoid walls. I will never forget that experience when I was 9-10 years old and get back to code at 23.
-
Oh yeah Google why don't you just change the parameter order of functions, remove entire functions between minor versions, and not put a single example on your API docs? And force devs to add 30 lines of boilerplate and start an http server so I can run the debugger? Fuck tensor flow, I'm moving to pytorch.2
-
Were ganno play a game: whoever forgets to remove prints() inside of his commits has to da an allnighter to fix the most difficult issue.
-
All these rubber ducks and here I dont feel like I need one when who ever I allow socialise with me, will do just fine. Maybe I have yet to experiance the joy of one and not its social status in the community :( i feel so out right now1
-
One of the worst practices in programming is misusing exceptions to send messages.
This from the node manual for example:
> fsPromises.access(path[, mode])
> fsPromises.access('/etc/passwd', fs.constants.R_OK | fs.constants.W_OK)
> .then(() => console.log('can access'))
> .catch(() => console.error('cannot access'));
I keep seeing people doing this and it's exceptionally bad API design, excusing the pun.
This spec makes assumptions that not being able to access something is an error condition.
This is a mistaken assumption. It should return either true or false unless a genuine IO exception occurred.
It's using an exception to return a result. This is commonly seen with booleans and things that may or may not exist (using an exception instead of null or undefined).
If it returned a boolean then it would be up to me whether or not to throw an exception. They could also add a wrapper such as requireAccess for consistent error exceptions.
If I want to check that a file isn't accessible, for example for security then I need to wrap what would be a simple if statement with try catch all over the place. If I turn on my debugger and try to track any throw exception then they are false positives everywhere.
If I want to check ten files and only fail if none of them are accessible then again this function isn't suited.
I see this everywhere although it coming from a major library is a bit sad.
This may be because the underlying libraries are C which is a bit funky with error handling, there's at least a reason to sometimes squash errors and results together (IE, optimisation). I suspect the exception is being used because under the hood error codes are also used and it's trying to use throwing an exception to give the different codes but doesn't exist and bad permissions might not be an error condition or one requiring an exception.
Yet this is still the bane of my existence. Bad error handling everywhere including the other way around (things that should always be errors being warnings), in legacy code it's horrendous.6 -
I need to tell you the story of my MOAB (Mother of all bugs).
I need to write some stuff in C (which i am fairly used to) and have a function that allocates memory for a Matrix on the heap. The matrix has a rows and columns property and an associated data array, so it looks like this
struct Matrix{
uint8_t rows;
uint8_t columns;
uint8_t data[];
}
I allocate rows*columns + 2 bytes of memory for it.
I also have a function to zero it out which does something like this
for(int i=0; i < rows*columns;i++){
data[i]=0;}
Let‘s come to the problem:
On my Mac the whole stuff works and passes all tests. We tried the code on a Linux machine and suddenly the code crashed in various places, sometimes a realloc got an invalid pointer, sometimes free got an invalid pointer and basically the code crashed at arbitrary points randomly.
I was confused af because did i really make THAT many errors?
I found out that all errors occured when testing my matrices so i looked more into it and observed it through the debugger.
Eventually i came to the function that zeroes out my matrix and it went unusually high and wondered if my matrix really was that big.
Then i saw it
The matrix wasn‘t initialised yet
It had arbitrary data that was previously in the heap.
It zeroed out a huge chunk of the heap space.
It literally wrote a zero to a shitload of addresses which invalidated many pointer.
You can imagine my facepalm2 -
Bloody fucking Android! Updates, updates and more updates! My development Nexus 5X won't allow me to sideload apps since it updated... Hello, printf debugging! Goodbye, profiler and debugger!
My hate for Android grows with each version after 4.0.$something... 2 was shit, I missed 3, 4 was OK, and since then it's going steeply down.
And don't get me started on Material Design...! Good luck figuring out what's a button and what's a label...
And what's up with the "let's keep all apps running all the time to save a few ms on start" philosophy!? Who thought that is a good idea!? Yeah, System.exit(0) works, but... Is it so hard to determine when it's not needed anymore (has no services running etc.)? Why should a web browser (for example) stay in memory after I quit? Minimize is a thing (Home button), why make it so confusing?
Another thing - feedback-less async tasks - why? I like to know when it is working in the background... How the hell am I supposed to find out if it is supposed to do this or if it is frozen?
And Android deciding to kill your process whenever it pleases without any callback... Happened to me once with an Activity in the foreground (no exceptions anywhere in my app, it just quit). How do you do IO properly? It seems you can't guarantee some file or socket or something that must be closed doesn't stay open (requiring to restart Bluetooth 'cause the socket wasn't closed, for example)...5 -
Working with Crystal reports, getting ready to deploy my changes. Guess what? My tiny changes to output has successfully broken 12 other fields, and 1 that is in absolutely no way related! Comes right from the database!
And it's crystal, so there's no debugger or logging. Plus, the report takes an hour to run! Today's gonna be a fun one!6 -
What we should do:
1. Find problem
2. Stop debugger
3. Change code
4. Restart debugging
What we all do:
1. Find problem
2. Forget about the debugger and change code immediately
3. Stop and Restart debugging -
New Project
M: Hey, check these two processes. Both took different paths for the same input. Here are the logs. Both are the same though.
Me: Ok... do we have a debugger?
M: No this product doesn't have a debugger
Me: Any unit tests i should know of?
M: We don't do unit testing. Everything is done in Integration Testing.
Me: Ok. So how can i check the db for this?
M: You can't, the access is restricted. You'll have to raise a ticket to other team with the sql output you need.
Me: Ok. So I hope you have the schema at least.
M: Yes we have the schema. But there was some issue last week so the values might not be there in the correct column. They may or may not be present where they are supposed to be.
Wtf am i supposed to do... fucking play football on ticketing system with the other team 😐1 -
WHY DOES EVERYTHING BREAK WHEN I WANT TO DEPLOY?
Finally fixed the last few bugs on my project and the thing is pretty much set to go. Then both the production and my local copy (identical in every way except for connecting to different MySQL servers) have the EXACT same query issues. The cursor fetch methods ALL get nothing EVEN WHEN I CAN SEE THE CURSOR HAS THE DATA I REQUESTED in the debugger.
I'm already in hot water for taking longer than expected with this project and this is going to push it back even further. -
Has anyone else ever used Matlab and wished other languages had a similar setup? The coding window, repl, variables window and the debugger, all of which are constantly connected?6
-
About ready to murder Xdebug...debugging an issue on a Drupal site and the debugger catches fine if I set a breakpoint in index.php, but breakpoints in any other file do not catch, even though die statements show that code is being executed where the breakpoint is set.3
-
What kind of fucking IDE changes the order of the open file tabs randomly?!?
I need to deal with multiple files and I really don't want to search for the file tab every fucking time I need it! It even gives the option to move tabs around as to arrange them as you wish. How is that helpful when the next time a file is opened the arrangement goes to hell?!
Fuck. I wish this IDE didn't have such a good debugger so I'm not stuck with it.1 -
VSCode doesn't (seem to) have the option to target specific sourcemaps, and ParcelJS doesn't have the option to specify the names of sourcemaps.
This fucks me over pretty hard since vscodes debugger expects the sourcemap to end in .js.map, but parcel gives me just .map. If the sourcemap doesn't end with .js.map vscode will just open the debug control panel pop up thing, wait a few seconds, and then close it again.
This has given me a new permanent temporary hack :v
https://github.com/inabahare/lewd2/...2 -
WHY??!!! doesn't the metadata reflect in the facebook debugger or when you post on linkedin for / random amounts of time! sometimes a minute / some times 7 hours... ugh. I cleared the cash - and everything I can think of.
-
I always love when I pick C again just for fun. I'm really used to "print" something if I'm not sure about that in basically everything.
You wanna print something in C? Well unless you know what and where it is (no point of print-checking then), it'll just happily crash without any reported error. Not to mention if I wanna find a bug, I don't have to get a debugger! Printf alone is basically a breakpoint! Ah stupid me :D -
Anyone ever try Tomcat debugging in VS Code? Specifically with Kotlin? I'm starting to get real fed up with IntelliJ tbh... it keeps screwing up when I have a multi-project/module workspace.
-
nano or IDLE, depending on need.
nano is the best terminal text editor by far, as i don't wanna have to learn a new command line and 2 control modes just to type in ffffffffffucking vim and it's just powerful enough to do what is needed without extra crap on top.
IDLE is super-light-weight, has a somewhat-handy debugger if i need to see what's up when my code interacts with modules or some such, takes up very little RAM and is open-source. Works exactly as needed and no more. -
i compiled an app on mingw on linux, for windows using qt4, when trying to run it on windows it crashes with no understandable error, i installed wine and tried to run it there, got a proper error message, it was missing dlls
before someone tells me, i know i need a debugger, I'm just hello worlding around to check that i have all headers and libs in place on both linux native and mingw -
With C++11, fell in love with std::enable_if and others in type_traits.
Lets you take generic programming to a whole new level. I never used it when this was part of boost thinking it didn't make as much sense. Now, I like to qualify my template definitions to be as restrictive as possible based on the expected usage. -
This is influenced by my current situation but best tool: Visual Studio. Versatile and rich debugger, good language integration for what I do. Worst tool: eclipse. What the fuck is this permacrashing nightmare of an application. And what the actual fuck are these keybinds.1
-
Debugger chip attached to my brain. That would save me so much time and effort. Also some money from not needing to buy state-of-the-art programming tools.1
-
Okay chrome debugger extension in vs code where the fuck is my page. Why the hell cant I see it you hateful son of a bitch.
-
I will be releasing first project to production. What I should know? What to turn off/on? Like debugger, redirects from old site etc. Thanks!2
-
Being told all those crazy startup ideas by friends and family with the comment "this is so simple, I'm sure I can learn to code and do it in 2 weeks"
-
I just realized that I have actually mastered the ways of the rubber duck debugger with the help of ... stackoverflow.
I just couldn't get my head around a problem thought about it for hours.
Googled for similar solutions, but didn't find anything.
In the end, I decided I'd do something I usually wouldn't and post a question on stackoverflow.
While carefully writing out and explaining my problem, it just made click.
I had it...
It works now...2 -
Introducing the quantum symbol.
I have a function throwing an error when passed a vector which has an unexpected size.
When I use the debugger and try to watch said vector for write access, the code which failed at some point just does… things. I have no idea what it is doing instead of failing but it is doing it gladly. It's not even paused, at least for the debugger.
Now I know why they said C++ is challenging to debug.10 -
I want to defenestrate the bright spark who came up with JQuery.
Not really, but its fucking hard to use without a proper debugger. A pox on Visual Studio. -
When the Verilog95 RTL coder tells you your debugger for object oriented SystemVerilog is primitive #stickuphisass
-
GDB&Code::Blocks got drunk together and this is apparently normal now. For like an hour already.
I DIDN'T RUN ANY FUCKING CODE IN BETWEEN THESE COMMANDS WTF IS THE DEBUGGER DOING ????
3 -
My first day of the "pool" in my school ended. Finally, the first day was learning how to properly use Unix systems. The "Moulinette" has to pass and validate the results, but we can't call it when we want. That's like a debugger that pass at fixed hours...
-
Everything that isn't code drives me nuts. Like build scripts? How do those even. And I always find myself fighting against my IDE to do simple things. And how do I use a debugger? Println statements only take me so far.
-
On the one hand, I'm done with all of the major bugs in a piece we're getting ready to launch this month.
On the other hand, there's one lingering bug that only appears when I've got Query Monitor running, because WooCommerce throws a false positive "table does not exist" error, which it tries to backtrace through **39** layers of functions, eating all of the memory.
Turning off Query Monitor fixes this, but means I basically have to flip it off before the primary function of the software and flip it back on afterward.
Currently considering the best way to put off the WooCommerce activation for a point where there isn't so much going on... -
It always seems that debugging tools are almost impossible to find for the language youre learning.
Here's an entire tutorial on Go - last chapter is how to use the debugger. GAHHHH -
To all React developers out there:
have you ever used the "so famous" Redux Time Machine Debugger capabilities?
Every now and then I see articles praising that as "one of the greatest things in Redux", but I either didn't understand the feature enough to see usage, or my applications are "way too CRUD"(?) to warrant time-traveling debugging.
Please, someone enlighten me :)3
Top Tags
Weekly Rant
View