Csysdig Explained Visually | Container Troubleshooting | Sysdig
Csysdig is an open source, htop-like interactive troubleshooting tool for Linux that is designed for monitoring and debugging containers. It understands Docker, Rkt and LXC containers and underlying processes and threads together with their resources usage (CPU, Memory, net and file IO, etc) – basically everything you can capture from system calls. It can also map container activity to related Kub
GitHub - alibaba/arthas: Alibaba Java Diagnostic Tool Arthas/Alibaba Java诊æ–利器Arthas
Often times, the production system network is inaccessible from the local development environment. If issues are encountered in production systems, it is impossible to use IDEs to debug the application remotely. More importantly, debugging in production environment is unacceptable, as it will suspend all the threads, resulting in the suspension of business services. Developers could always try to
Mark J. Wielaard » Blog Archive » dtrace for linux; Oracle does the right thing
At Fosdem we had a talk on dtrace for linux in the Debugging Tools devroom. Not explicitly mentioned in that talk, but certainly the most exciting thing, is that Oracle is doing a proper linux kernel port: commit e1744f50ee9bc1978d41db7cc93bcf30687853e6 Author: Tomas Jedlicka <tomas.jedlicka@oracle.com> Date: Tue Aug 1 09:15:44 2017 -0400 dtrace: Integrate DTrace Modules into kernel proper This ch
[新機能] Lambda 関数ã®ãƒã‚°ãŒç°¡å˜ã«è¦‹ã‚‰ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸï¼ #reinvent | DevelopersIO
CloudWatch Logs ã¸ã‚¸ãƒ£ãƒ³ãƒ— re:Invent 2017 ã§ç™ºè¡¨ã•ã‚ŒãŸ AWS Lambda ã®æ–°æ©Ÿèƒ½ã§ã™ã€‚ Lambda コンソールã‹ã‚‰ CloudWatch Logs ã¸ã®é·ç§»ãŒç°¡å˜ã«è¡Œãˆã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸã€‚ æ‰‹é † Lambda 関数ã®ãƒã‚°ãŒãƒ¯ãƒ³ã‚¿ãƒƒãƒã§ç¢ºèªã§ãるよã†ã«ãªã£ãŸã®ã§ã€ãƒ‡ãƒãƒƒã‚°ãŒæ—ã‚Šãã†ã§ã™ã€‚ ãªãŠã€ã‚°ãƒ©ãƒ•ã¯ãƒžã‚¦ã‚¹ã§ãƒ‰ãƒ©ãƒƒã‚°ã™ã‚‹ã“ã¨ã«ã‚ˆã‚Šã‚ºãƒ¼ãƒ インã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚（ダブルクリックã§ã‚ºãƒ¼ãƒ アウト） ãŠè©¦ã—ãã ã•ã„。 ↓ リンク AWS re:Invent 2017: What's New in Serverless (SRV305) | YouTube ミレニアム・ファルコン製作日記 #100 100 å· è¡¨ç´™ パーツ 完æˆï¼ï¼ 今回ã®ä½œæ¥ã¯ä»¥ä¸‹ã® 2 ã¤ã§ã—ãŸã€‚ ディテールパーツをå–り付ã‘ã‚‹ リモートコントãƒãƒ¼ãƒ«ã‚’セットã™ã‚‹ 完çµå·ã®ä»Šå·ã§ã¯ã€ã“ã‚Œã¾ã§ã«
![[新機能] Lambda 関数ã®ãƒã‚°ãŒç°¡å˜ã«è¦‹ã‚‰ã‚Œã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸï¼ #reinvent | DevelopersIO](https://cdn-ak-scissors.b.st-hatena.com/image/square/acd28bc9c3783593f59998f1df4f97183f4927bb/height=288;version=1;width=512/https%3A%2F%2Fdevio2023-media.developers.io%2Fwp-content%2Fuploads%2F2017%2F10%2Freinvent2017_eyecatch.png)
debugCSS : (X)HTML debugging tool built with CSS
debugCSS: (X)HTML debugging tool built with CSSdebugCSS is meant to be loaded on an existing page to highlight potentially broken, malformed or legacy (X)HTML. Not all "errors" are created equally, so they are color coded to highlight severity. Green is "probably not a big problem", yellow is "worth looking at" and red is "you really should fix this." Click and drag the link below to your bookmark
Go has a debugger—and it's awesome!
Something that often, uh... bugs[1] Go developers is the lack of a proper debugger. Sure, builds are ridiculously fast and easy, and println(hex.Dump(b)) is your friend, but sometimes it would be nice to just set a breakpoint and step through that endless if chain or print a bunch of values without recompiling ten times. CC BY 2.0 image by Carl Milner You could try to use some dirty gdb hacks that
Chrome/Firefox ã® JavaScript Debugger ã§ã‚¹ãƒ†ãƒƒãƒ—実行時ã«ãƒ©ã‚¤ãƒ–ラリ・フレームワークをスã‚ップã™ã‚‹ - Qiita
JavaScript ã®ãƒ‡ãƒãƒƒã‚¬ã€ä¾¿åˆ©ã§ã™ã‚ˆã。ã¤ã‹ã£ã¦ã€ã¾ã™ã‚ˆã! Chrome, Firefox 両方㮠Developer Tool (Web Inspector) ã«ã¯ JavaScript デãƒãƒƒã‚¬ãŒä»˜å±žã—ã¦ã„ã¾ã™ã€‚両者ã«ã¯ Event Listener Breakpoints 機能ãŒå˜åœ¨ã—ã€ç‰¹å®šã‚¤ãƒ™ãƒ³ãƒˆã®ãƒªã‚¹ãƒŠå…¨éƒ¨ã«ãƒ–レークãƒã‚¤ãƒ³ãƒˆã‚’仕掛ã‘る事ãŒå¯èƒ½ã§ã™ã€‚ ã—ã‹ã—ã€jQuery ã® $.on, $.bind, ãã®ä»– $.click(fn) ç‰ã§ã‚¤ãƒ™ãƒ³ãƒˆãƒãƒ³ãƒ‰ãƒ©ã‚’定義ã™ã‚‹ã¨ jQuery ã®ä¸ã§ addEventListeners ãŒå‘¼ã°ã‚Œå†…部ã§å‡¦ç†ã‚’ã—ãŸå¾Œã«å®Ÿéš›ã« jQuery ã«æ¸¡ã—ãŸé–¢æ•°ãŒå‘¼ã°ã‚Œã¾ã™ã€‚ ãã®ãŸã‚ã€JavaScript デãƒãƒƒã‚¬ã¯ jQuery 内部ã§ãƒ–レークã—本æ¥é£›ã‚“ã§ã»ã—ã„ã¯ãšã®é–¢æ•°ã«ä¸€ç™ºã§é£›ã‚“ã§ãã‚Œã¾ã›ã‚“。 ãã“㧠Firefox ã«ã¯ Library
segv-handler-gdb：RubyスクリプトãŒã‚¯ãƒ©ãƒƒã‚·ãƒ¥ã—ãŸã¨ãã«ã‚ˆã‚Šè©³ã—ãCレベルã®ãƒãƒƒã‚¯ãƒˆãƒ¬ãƒ¼ã‚¹ã‚’出力ã™ã‚‹gem - 2013-10-31 - ククãƒã‚°
æ ªå¼ä¼šç¤¾ã‚¯ãƒªã‚¢ã‚³ãƒ¼ãƒ‰ > ククãƒã‚° > segv-handler-gdb：RubyスクリプトãŒã‚¯ãƒ©ãƒƒã‚·ãƒ¥ã—ãŸã¨ãã«ã‚ˆã‚Šè©³ã—ãCレベルã®ãƒãƒƒã‚¯ãƒˆãƒ¬ãƒ¼ã‚¹ã‚’出力ã™ã‚‹gem Rubyã§æ‹¡å¼µãƒ©ã‚¤ãƒ–ラリーを使ã£ã¦ã„ã‚‹ã¨ã‚¯ãƒ©ãƒƒã‚·ãƒ¥ã™ã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚自分ãŒé–‹ç™ºã—ã¦ã„る拡張ライブラリーãªã‚‰ã©ã†ã«ã‹ã—ã¦ç›´ã—ãŸã„ã‚‚ã®ã§ã™ã€‚ãã®ã¨ãã«å½¹ç«‹ã¤ã®ãŒGDBãªã©ã®ãƒ‡ãƒãƒƒã‚¬ãƒ¼ã§ã™ã€‚Cレベルã®ã‚ˆã‚Šè©³ç´°ãªæƒ…å ±ã‚’å–å¾—ã§ãã‚‹ãŸã‚ã€å•é¡Œã®ç‰¹å®šã«å½¹ç«‹ã¡ã¾ã™ã€‚ã—ã‹ã—ã€æ¬¡ã®ã‚ˆã†ã«ãƒ‡ãƒãƒƒã‚¬ãƒ¼ä¸Šã§ã‚¯ãƒ©ãƒƒã‚·ãƒ¥ã•ã›ã‚‹ã“ã¨ãŒé›£ã—ã„ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚ GDB上ã§å‹•ã‹ã™ã¨ã‚¯ãƒ©ãƒƒã‚·ãƒ¥ã—ãªã„ 消極的ãªç†ç”±ã§ã™ãŒæ¬¡ã®ã‚ˆã†ãªã‚±ãƒ¼ã‚¹ã‚‚ã‚ã‚Šã¾ã™ã€‚ ãªã‹ãªã‹ã‚¯ãƒ©ãƒƒã‚·ãƒ¥ã—ãªã„ã®ã§ã€ãšã£ã¨GDB上ã§å‹•ã‹ã—ã¦ã„ã‚‹ã‚ã‘ã«ã‚‚ã„ã‹ãªã„ SIGPIPEãªã©ã‚’æ•ã¾ãˆã¦æ¢ã¾ã£ã¦æ¬²ã—ããªã„。「handle SIGPIPE nostopã€ãªã©ã‚’ã™ã‚‹ã®ãŒé¢å€’。 クラッシュã—ãŸã‚‰è‡ªå‹•ã§èµ·å‹•ã—
Coreã‹ã‚‰Rubyã®ãƒãƒƒã‚¯ãƒˆãƒ¬ãƒ¼ã‚¹ã‚’表示ã™ã‚‹gdbruby.rbを作ã£ãŸ
gdbperl.plã¨ã„ã†ã‚¹ã‚¯ãƒªãƒ—トãŒã‚ã‚Šã¾ã™ã€‚ãんｋã™ã‚‹æ¨‹å£è¨¼ã•ã‚“作ã®ã€gdbã‚’æ“作ã—ã¦Perlã®ãƒ—ãƒã‚»ã‚¹ã®ãƒãƒƒã‚¯ãƒˆãƒ¬ãƒ¼ã‚¹ã‚’å–るツールã§ã™ã€‚生ãã¦ã„るプãƒã‚»ã‚¹ã ã‘ã§ã¯ãªãã€coreã‚’å–ã£ã¦ãŠã‘ã°ãã®coreã‹ã‚‰ãƒãƒƒã‚¯ãƒˆãƒ¬ãƒ¼ã‚¹ãŒå–れるã®ãŒç‰¹å¾´ã§ã™ã€‚ gcoreã¨ã„ã†ã‚³ãƒžãƒ³ãƒ‰ãŒ/usr/binã‚ãŸã‚Šã«ã‚ã£ã¦ã€ã“れを使ãˆã°èµ°ã£ã¦ã„るプãƒã‚»ã‚¹ã®coreã‚’å–å¾—ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚よã£ã¦ã€æœ¬ç•ªç’°å¢ƒã§æ°—軽ã«coreã‚’å–ã£ã¦gdbperl.plã«ã‹ã‘ã‚‹ã“ã¨ã«ã‚ˆã£ã¦ã€åˆºã•ã£ã¦ã„ã‚‹ãƒã‚¤ãƒ³ãƒˆã‚’見ã¤ã‘ãŸã‚Šã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚超便利。 ãã‚ã—ãã¯ã€Perlスクリプトをgdbã§ãƒ‡ãƒãƒƒã‚°ã‚’å‚ç…§ãã ã•ã„。 ã‚“ã§ã€ãã®ä¾¿åˆ©ãªgdbperl.plã‚’Rubyã«ç§»æ¤ã—ã¦ã¿ã¾ã—ãŸã€‚ãã®åã‚‚gdbruby.rb。å˜ç´”。 gdbruby.rb 使ã„æ–¹ã¨ã‹ Rubyã¯ãƒ‡ãƒãƒƒã‚°ã‚·ãƒ³ãƒœãƒ«ä»˜ãã®ã‚‚ã®ã‚’ã”用æ„ãã ã•ã„。 生ãã¦ã„るプãƒã‚»ã‚¹ã«ã‚¢
GitHub - hirose31/inspect-perl-proc: get %INC and dump into file
#!/usr/bin/env perl use strict; use warnings; use Getopt::Long qw(:config posix_default no_ignore_case no_ignore_case_always permute); use Pod::Usage; use Carp; my $PROG = substr($0, rindex($0, '/')+1); my $Debug = 0; sub dprint (@) { return unless $Debug; my @m = @_; chomp @m; print STDERR @m,"\n"; } MAIN: { my $target_pid; my $mode; GetOptions( 'pid|p=i' => \$target_pid, 'mode|m=s' => \$mode, 'd
Native Memory Tracking in 7u40 – Marcus Hirt
Since we don’t have any nice NMT (Native Memory Tracking) MBean in HotSpot (yet), and therefore not in the JMC console, I thought I’d show how it can be done using command line arguments and JCMD. Please note that you’ll get a 5-10% performance hit if you enable this. Step 1 – Enabling NMT This is done by using the following command line: -XX:NativeMemoryTracking=[off|summary|detail] Where the dif
)
Windows: Windows ã®é™ç•Œã«æŒ‘ã‚€: ãƒãƒ³ãƒ‰ãƒ«
ã“ã®è¨˜äº‹ã¯ã€ã€ŒWindows ã®é™ç•Œã«æŒ‘ã‚€ã€ã‚·ãƒªãƒ¼ã‚ºã® 5 回目ã®æŠ•ç¨¿ã§ã™ã€‚ã“ã®ä¸€é€£ã®è¨˜äº‹ã§ã¯ã€ç‰©ç†ãƒ¡ãƒ¢ãƒªã€ä»®æƒ³ãƒ¡ãƒ¢ãƒªã€ãƒ—ãƒã‚»ã‚¹ã€ã‚¹ãƒ¬ãƒƒãƒ‰ãªã©ã€Windows ã§ç®¡ç†ã§ãるリソースã®æ•°é‡ã¨ã‚µã‚¤ã‚ºã®ä¸Šé™ã«ã¤ã„ã¦æ‰±ã£ã¦ãã¾ã—ãŸã€‚ Windows ã®é™ç•Œã«æŒ‘ã‚€: 物ç†ãƒ¡ãƒ¢ãƒª Windows ã®é™ç•Œã«æŒ‘ã‚€: 仮想メモリ Windows ã®é™ç•Œã«æŒ‘ã‚€: ページ プールã¨éžãƒšãƒ¼ã‚¸ プール Windows ã®é™ç•Œã«æŒ‘ã‚€: プãƒã‚»ã‚¹ã¨ã‚¹ãƒ¬ãƒƒãƒ‰ 今回ã¯ã€ãƒãƒ³ãƒ‰ãƒ«ã®å®Ÿè£…ã®é™ç•Œã‚’探りã€è§£èª¬ã—ã¾ã™ã€‚ãƒãƒ³ãƒ‰ãƒ«ã¯ã€ã‚¢ãƒ—リケーションãŒæ“作ã™ã‚‹åŸºæœ¬çš„ãªã‚ªãƒšãƒ¬ãƒ¼ãƒ†ã‚£ãƒ³ã‚° システムã®ã‚ªãƒ–ジェクト (ファイルã€ãƒ¬ã‚¸ã‚¹ãƒˆãƒª ã‚ーã€åŒæœŸãƒ—リミティブã€å…±æœ‰ãƒ¡ãƒ¢ãƒªãªã©) ã®é–‹ã‹ã‚Œã¦ã„るインスタンスを表ã™ãƒ‡ãƒ¼ã‚¿æ§‹é€ ã§ã™ã€‚1 ã¤ã®ãƒ—ãƒã‚»ã‚¹ãŒä½œæˆã§ãã‚‹ãƒãƒ³ãƒ‰ãƒ«ã®æ•°ã«ã¤ã„ã¦ã¯ã€2 ã¤ã®åˆ¶é™ãŒã‚ã‚Šã¾ã™ã€‚システムã§è¨å®šã•ã‚Œã¦ã„るプãƒã‚»ã‚¹ã”ã¨ã®ãƒãƒ³
シェルスクリプトã®ãƒ‡ãƒãƒƒã‚°ã¯ typeset ã¾ãŸã¯ declare を使ã†ã¨è‰¯ã„ã‹ã‚‚ - よんã¡ã‚…Blog
ã¯ã˜ã‚ã« ã¤ã„最近知ã£ãŸä¾¿åˆ©ãªãƒ‡ãƒãƒƒã‚°æ–¹æ³• (長年シェルスクリプトを書ã„ã¦ã„ã‚‹ã®ã«çŸ¥ã‚‰ãªã‹ã£ãŸã€‚ã“ã‚ŒãŒå¸¸è˜ã ã£ãŸã‚‰æ¥ãšã‹ã—ã„…) シェルスクリプトã®ãƒ‡ãƒãƒƒã‚°ã§ã¯ echo ã§å¤‰æ•°ã®ä¸èº«ã‚’見るã¨ã„ã†åŽŸå§‹çš„ãªæ–¹æ³•ã‚’よã使ã†ã‹ã¨æ€ã„ã¾ã™ã€‚ ã„ã‚ゆる プリントデãƒãƒƒã‚° ã¨ã„ã†ã‚„ã¤ã§ã™ã。 ã‚‚ã†å°‘ã—詳ã—ã„デãƒãƒƒã‚°ãŒå¿…è¦ãªå ´åˆã¯ã€ set -x 㨠set +x ã§ãƒ‡ãƒãƒƒã‚°ã—ãŸã„部分を囲むã¨ã„ã†æ–¹æ³•ã‚‚ã‚ã‚Šã¾ã™ã€‚ 今回㯠プリントデãƒãƒƒã‚° ã§ä½¿ã† echo ã®ä»£ã‚ã‚Šã« typeset or declare を使ã†ã¨è‰¯ã„ã¨ã„ã†ãŠè©±ã§ã™ã€‚ プリントデãƒãƒƒã‚°ã¯ typeset or declare を使ãŠã† typeset or declare ã¯å¤‰æ•°å®£è¨€ãªã©ã§ã‚ˆã使ã†ã‚³ãƒžãƒ³ãƒ‰ã§ã™ãŒã€å¤‰æ•°ã®ä¸èº«ã‚’見るã®ã«ã‚‚使ãˆã¾ã™ã€‚ echo ã¨æ¯”ã¹ã¦ä½•ãŒè‰¯ã„ã®ã‹ã¨ã„ã†ã¨ã€å¤‰æ•°ã®ä¸èº«ã¯ã‚‚ã¡ã‚ん変数åや変数ã®åž‹ã‚‚表示ã—ã¦ãã‚Œã€
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
GitHub - WuBingzheng/memleax: debugs memory leak of running process. Not maintained anymore, try `libleak` please.
GitHub - RudjiGames/MTuner: MTuner is a C/C++ memory profiler and memory leak finder for Windows, PlayStation 4 and 3, Android and other platforms
GitHub - MicrosoftDX/Vorlonjs: A new, open source, extensible, platform-agnostic tool for remotely debugging and testing your JavaScript. Powered by node.js and socket.io
GitHub - jgrahamc/httpdiff: Perform the same request against two HTTP servers and diff the results
Ruby プãƒã‚»ã‚¹ã‚’追ã„ã‹ã‘るツール(プãƒãƒ•ã‚¡ã‚¤ãƒ©ã¨ã‹)10é¸ - sonots:blog
Microsoftã€ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯è§£æžãƒ„ール「Microsoft Message Analyzerã€ã‚’æ£å¼å…¬é–‹
How to get a stacktrace with WinDbg - Mozilla | MDN
{{#tags}}- {{label}}
{{/tags}}