View allAll Photos Tagged debugging
What the hell is going on here?
Yellow is SDA, Green is SCL
Master is sending an address of 0x70 (b1110000), and a slave read bit (0). Then it's supposed to ACK on a 9th clock cycle, which never happens.
UPDATE: problem solved.
This is the call stack from top to bottom when an individual Drupal node is loaded -- focuses only on the views_playlist.module functions that are called. The debug_print_backtrace(); php command was placed at the beginning of each function, and then a node was loaded.
I then did a view source, and then did some text replacements to get rid of extra line breaks, and place two line breaks at the beginning on a new stack trace (i.e. with each instance of #0).
These are the text replacements I did in Microsoft Word
REPLACE ^p# WITH TEMPTEXTFLAG#
REPLACE ^p WITH ""
REPLACE TEMPTEXTFLAG# WITH ^p#
REPLACE ^p#0 WITH ^p^p#0
REPLACE "called at " with ^t
I could then import the data into MicroSoft Excel.
I then
A1 = 1 and in A2 =
=IF(E2="",A1+1,A1)
B1 = 0 and B2 =
=IF(E2="",-1,B1+1)
That gave columns that looked like
1 0
1 1
1 2
1 3
1 3
I copied column A & B and then did a paste by value via "Paste Special..." I selected columns A through D, and sorted first by Column A (ascending), and then Column B (descending) This showed the chronological order in which the functions were called.
I then copied the cell values from the excel spread sheet into omnigraffle pro where the were treated as a single object. I had to paste multiple sections and group them together so that I could copy it, and then paste it into Preview. Once it was in preview, then I could export it as a PNG and then upload it here.
I'm a geek.
0x34 is sent MSBit-first. Data is driven on the rising edge, sampled on the falling edge.
Immediately after the last bit is sampled, the data direction changes and the target asserts the line.
playing with some new ideas involving desktop segmentation over time... tracking usage... public information & sharing....
For connecting a chipKIT™ board to the Microchip® PICkit™ 3 debugger/programmer. Includes a 6" 6-pin cable, a 6-pin gender changer, and a 6-pin right angle male header.
Haven't tracked down the cause of this perimeter retraction issue while printing with the latest PLA. Documenting it here for the moment.
Strange how it seems to be Z-height dependent.
Update: Turns out this was caused by a sticky filament spool.
This laptop was left turned on overnight in an area that was infested with flying ants.
The customer reported stability problems with the computer. No wonder! When stripped for cleaning this is what I found.
This computer lived on a lino floor behind a counter in a business. There were covers missing on the rear of the case. There were also other holes in various places. The computer was left running most of the time - offering a nice warm environment.
Result? Mice moved in, bugs moved in, geckos moved in... the system was a mess internally. Some of the liquid wasts of these infecting mice/bugs/geckos/whatever had settled on the motherboard. I guess some of it was caustic enough to start eating away at the PCB tracks.
2017臺北國際動漫節第五日下午B舞臺，東立出版社＜Debug─筆電的使用手冊外傳小說~山櫻樹下的幻想奇譚＞作者草子信與插繪nyaroro簽名會。由於夜排、插隊（臺灣俗呼「解壓縮」）嚴重，下午2點30分活動開始前東立出版社工作人員要求重排，領號碼牌過程中發生推擠衝突，有書迷因而負傷，事後東立出版社在官方臉書上公開致歉。攝影者拍攝時遭工作人員制止，當時不解其故，回家後查新聞方知。
備考：
X is time, Y is VCC. Points are plotted for any error when the chip is not locked, with the histogram at the bottom giving a decent indication of current consumption at that moment in time.
The glitch plan is in blue, while ignored points are in red. I'm targeting the reset moment (X in [0,2]) as well as the first few power spikes as flash is initialized and the chip begins to be debugged (X in [53,80]).
I'm trying to debug Apple's SceneKit (because crashes are reported from within the SceneKit binaries) and found a way to show Flatland with normals, which is a way of saying Flatland is showing which part of each point on the surface is perpendicular to the surface. It's pretty, but disappointing I have to resort to this to get my program to work.
...evening debug. A PJRC Teensy 3.1, Sparkfun LiPo battery charger, and Sparkfun breakout board with MPU-6050 IMU. (This work is licensed under a Creative Commons Attribution 4.0 International License. Please provide attribution and a link back to this web page in a manner that associates the image with the image credit.)
Early tests show that disconnecting the SYS_5V pins fixes the powerdown issue. Only 40 more pins to connect.
HE HAS REVISED DEBUG SETTINGS FOR YOUR JOY
» wiki.secondlife.com/wiki/Debug_Settings
ENJOY
Posted by Second Life Resident Torley Linden. Visit Beaumont.
Screenshot of the new feature in nemiver of extracting the list of source files from the target executable that is being debugged. Here Nemiver is debugging itself.
this is the kind of code i hate. i am debugging someone else's code right now and let me tell you it stinks to high heaven.
It was time to de-hair the carpet attachment. And this time just an exacto along the bottom wasn't enough. I had to clean out the bearings.
To my delight, the disassembly was quick and painless. It required no special screwdrivers. Nothing was glued together. In fact, there were even helpful notes printed in plastic. *AND* a little schematic diagram included to assist in debugging or maintaining the motor and light!
Kudos to Kenmore/Sears!
The other day I laid my hands on this so called "lord of the canon 35mm slrs" Canon EOS-1D at office. Bharat lost in his world of bugging and debugging.