*출처: https://www.tiobe.com/tiobe-index/


2018년 1월의 언어로 C언어가 선정되었습니다. 자동차 시장을 포함한 제조 및 기계 산업이 성장하는 것이 주요한 원인으로 보입니다. (주로 미국에서) 물론 오토모티브 분야는 국내에서도 거듭 새롭게 주목받고 있습니다. 자율주행 차량에 대한 관심이 계속되기 때문입니다.


Jan 2018Jan 2017ChangeProgramming LanguageRatingsChange
11Java14.215%-3.06%
22C11.037%+1.69%
33C++5.603%-0.70%
45changePython4.678%+1.21%
54changeC#3.754%-0.29%
67changeJavaScript3.465%+0.62%
76changeVisual Basic .NET3.261%+0.30%
816changeR2.549%+0.76%
910changePHP2.532%-0.03%
108changePerl2.419%-0.33%
1112changeRuby2.406%-0.14%
1214changeSwift2.377%+0.45%
1311changeDelphi/Object Pascal2.377%-0.18%
1415changeVisual Basic2.314%+0.40%
159changeAssembly language2.056%-0.65%
1618changeObjective-C1.860%+0.24%
1723changeScratch1.740%+0.58%
1819changeMATLAB1.653%+0.07%
1913changeGo1.569%-0.76%
2020PL/SQL1.429%-0.11%


https://docs.microsoft.com/en-us/sysinternals/downloads/procdump

Procdump.zip


소개

ProcDump는 관리자 나 개발자가 스파이크의 원인을 파악하는 데 사용할 수있는 스파이크 중 CPU 스파이크 및 크래시 덤프를 모니터링하는 것을 주된 목적으로하는 명령 줄 유틸리티입니다. 또한 ProcDump에는 중단 된 창 모니터링 (Windows 및 작업 관리자에서 사용하는 것과 동일한 창 정의 정의 사용), 처리되지 않은 예외 모니터링 및 시스템 성능 카운터 값을 기반으로 덤프를 생성 할 수 있습니다. 또한 다른 스크립트에 임베드 할 수있는 일반 프로세스 덤프 유틸리티로도 사용할 수 있습니다.

사용법

usage: procdump [-a] [[-c|-cl CPU usage] [-u] [-s seconds]] [-n exceeds] [-e [1 [-b]] [-f <filter,...>] [-g] [-h] [-l] [-m|-ml commit usage] [-ma | -mp] [-o] [-p|-pl counter threshold] [-r] [-t] [-d <callback DLL>] [-64] <[-w] <process name or service name or PID> [dump file] | -i <dump file> | -u | -x <dump file> <image file> [arguments] >] [-? [ -e]


'notepad'이라는 프로세스의 미니 덤프를 작성하십시오 (하나의 일치 항목 만 존재할 수 있음).

C : \> procdump
notepad

PID가 '4572'인 프로세스의 전체 덤프를 작성하십시오.

C : \> procdump -ma 4572

'메모장'이라는 프로세스의 5 초 간격으로 3 개의 미니 덤프를 작성하십시오.

C : \> procdump -s 5 -n 3
notepad

5 초 동안 CPU 사용량이 20 %를 초과하면 'consume'라는 프로세스의 최대 3 개의 미니 덤프를 작성하십시오.

C : \> procdump -c 20 -s 5 -n 3 consume

윈도우 중 하나가 5 초 이상 응답하지 않으면 'hang.exe'라는 프로세스의 미니 덤프를 작성하십시오.

C : \> procdump -h hang.exe hungwindow.dmp

총 시스템 CPU 사용량이 10 초 동안 20 %를 초과하면 'outlook'이라는 프로세스의 미니 덤프를 작성하십시오.

C : \> procdump outlook -p "\ Processor (_Total) \ % Processor Time"20

Outlook의 핸들 수가 10,000을 초과하면 'outlook'이라는 프로세스의 전체 덤프를 작성하십시오.

C : \> procdump -ma outlook -p "\ Process (Outlook) \ Handle Count"10000

처리되지 않은 예외가있을 때 Microsoft Exchange Information Store의 MiniPlus 덤프를 작성하십시오.

C : \> procdump -mp -e store.exe

덤프를 작성하지 않고 표시, w3wp.exe의 예외 코드 / 이름 :

C : \> procdump -e 1 -f ""w3wp.exe

예외 코드 / 이름에 'NotFound'가 포함 된 경우 w3wp.exe의 미니 덤프를 작성하십시오.

C : \> procdump -e 1 -f NotFound w3wp.exe

프로세스를 시작한 다음 예외를 모니터링합니다.

C : \> procdump -e 1 -f ""-x c : \ dumps consume.exe

시작을 위해 등록하고 현대적인 '응용 프로그램'을 활성화하십시오. 새로운 ProcDump 인스턴스는 예외를 모니터링하기 위해 활성화 될 때 시작됩니다 :

C : \> procdump -e 1 -f ""-x c : \ dumpsMicrosoft.BingMaps_8wekyb3d8bbwe! AppexMaps

현대 '패키지'출시를 위해 등록하십시오. 새로운 ProcDump 인스턴스가 (수동으로) 활성화 될 때 시작되어 예외를 모니터링합니다 :

C : \> procdump -e 1 -f ""-x c : \ dumps Microsoft.BingMaps_1.2.0.136_x64__8wekyb3d8bbwe

Just-in-Time (AeDebug) 디버거로 등록하십시오. c : \ 덤프에서 전체 덤프를 작성합니다.

C : \> procdump -ma -i c : \ dumps

예제 명령 줄 목록을 참조하십시오 (예제는 위에 나열되어 있습니다).

C : \> procdump -? -e







CMake binary files for Windows x64



cmake-bin-win-x64.zip


TODO:

- 64bit NSIS 등을 이용하여 설치 프로그램 작성

- cmake gui for x64 빌드 추가....



VIM 7.4(WIN32) VIM(WIN64)


vim, gvim


source from: http://www.vim.org/


VIM(gvim) 7.4 (WIndows-32bit)

gvim74.zip



VIM 7.3 (WIndows-64bit)

vim73-x64.7z.001


vim73-x64.7z.002


 

 

 

name2fo.xsl

<?xml version="1.0" encoding="utf-8"?>

<name>Frank</name>

 

name.xml

<?xml version="1.0" encoding="utf-8"?>

           <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format">

           <xsl:output method="xml" indent="yes"/>

           <xsl:template match="/">

                     <fo:root>

                                <fo:layout-master-set>

                                          <fo:simple-page-master master-name="A4-portrait" page-height="29.7cm" page-width="21.0cm" margin="2cm">

                                                     <fo:region-body/>

                                          </fo:simple-page-master>

                                </fo:layout-master-set>

                                <fo:page-sequence master-reference="A4-portrait">

                                          <fo:flow flow-name="xsl-region-body">

                                                     <fo:block>

                                                     Hello, <xsl:value-of select="name"/>!

                                                     </fo:block>

                                          </fo:flow>

                                </fo:page-sequence>

                     </fo:root>

           </xsl:template>

</xsl:stylesheet>

 

generate.cmd

@REM  Apache FOP (ver 1.0/1.1)

c:\FOP\fop -xml name.xml -xsl name2fo.xsl -pdf name.pdf

 

 

'정보기술' 카테고리의 다른 글

VIM 7.4(WIN32) VIM(WIN64) gvim  (0) 2014.02.15
프로그래머(Programmer)와 사용자(User)가 바라보는 상대방  (0) 2013.12.13
Apache FOP example : Generate a PDF  (0) 2013.10.29
NoFlo : Flow-Based Programming  (0) 2013.08.14
tor browser download  (0) 2012.11.06
NetMon, NEWT  (0) 2012.10.04


Getting started with NoFlo 

NoFlo is a Flow-Based Programming environment for JavaScript. In flow-based programs, the logic of your software is defined as a graph. The nodes of the graph are instances of NoFlo components, and the edges define the connections between them.

NoFlo components react to incoming messages, or packets. When a component receives packets in its input ports it performs a predefined operation, and sends its result out as a packet to its output ports. There is no shared state, and the only way to communicate between components is by sending packets.

NoFlo components are built as simple CoffeeScript classes that define the input and output ports, and register various event listeners on them. When executed, NoFlo creates a live graph, or network out of a graph, instantiates the components used in the graph, and connects them together.

NoFlo graphs can deal with multiple different input paradigms. The same flow can react to incoming HTTP requests, text messages, and changes in the file system, and can similarly output to different targets like writing to a database, responding to the HTTP requests, or updating a dashboard. It is simply a matter of choosing the components you want to use.

Using NoFlo 

There are two ways to run your flow-based programs with NoFlo. If your whole application is based on flows, you can simply have NoFlo execute and run it. Flow-based programs done in this way are called independent graphs. You can run them with the noflo command that ships with the NoFlo package.

The other option is to embed NoFlo graphs into your existing JavaScript application by using it as a regular Node.js library. This is useful when you already have an existing system where you want to automate some parts as their own flows, or to add new functionality.

Examples of embedded usage of NoFlo include handling billing processes or routing incoming SMS or email within an existing Node.js web application.

Activation model 

When you start a NoFlo network, it doesn't do anything by itself. It only loads the components of the graph and sets up the connections between them. Then it is up to the components to actually start sending messages to their outports, or reacting to messages they receive on their input ports.

Since most components require some input before they act, the usual way to make a NoFlo graph run is to send it some initial information packets, or IIPs. Examples of this would include sending a port number that a web server could listen to the web server component, or sending a file name to a file reader.

This activation model provides many possibilities:

  • Starting a flow based on user interaction (shell command, clicking a button)
  • Starting a flow based on a received signal (Redis pub/sub, D-Bus signal, WebHook, email)
  • Starting a flow at a given time or interval (running a graph on the first of every month, or five minutes from now)
  • Starting a flow based on context (when arriving to a physical location, when user goes to a given web site)

Creating a NoFlo project 

NoFlo projects are created in the same way as any other Node.js project would. To get started, you need a working installation of Node.js (version 0.8 or later), and the NPM package manager that comes with it.

You can test that your Node.js installation works by running:

$ npm -v

If this doesn't work, read the Node.js installation instructions for your operating system.

Project folder 

To create a new project, you should create a new folder in the file system. This folder will contain all the files specific to your project, including dependency declarations, unit tests, and the NoFlo graphs and components. This is what you’ll usually want to manage in version control.

$ mkdir my-noflo-example-app

Then go to that folder:

$ cd my-noflo-example-app

Installing NoFlo 

The first thing to do with your project is to create a package.json file into the project root. This is the file that is used by NPM for finding and installing the libraries your project needs.

A basic package.json file could look like the following. Create one using a text editor:

{
  "name": "my-noflo-example-app",
  "version": "0.0.1"
}

Once the package.json file is in place, you're ready to install NoFlo. Do this by running:

$ npm install noflo --save

NPM will fetch the latest release version of NoFlo and all its dependencies. Once this has finished, try that NoFlo works by running:

$ ./node_modules/.bin/noflo -h

Getting components 

The main NoFlo package gives you the environment for running flows. In addition you'll need the components that you'll be using in your graphs.

There are 250 open source components available via NoFlo Component Libraries that you can install with NPM.

For example, to install the filesystem components , you can run:

$ npm install noflo-filesystem --save

We should also install noflo-core , which provides various general utility components:

$ npm install noflo-core --save

Once NPM completes the components from that library will be available to your project. Your project can pull in components from as many NoFlo libraries as needed.

You can see a list of components that are installed in your project with:

$ ./node_modules/.bin/noflo list .

Defining your first graph 

All NoFlo programs are built as graphs, which define the nodes and components used, and connections between them.

NoFlo graphs can be either defined in a JSON file format or using the .fbp domain-specific language . For brevity, this guide uses the .fbp syntax.

Our first graph can be a simple one. Since we already have the file system components available, we can implement a graph that reads a file, and outputs its contents on the screen.

Graphs are typically stored in the graphs subfolder of a NoFlo project. Create that folder:

$ mkdir graphs

Create a new file in that folder called ShowContents.fbp and open it in your favorite text editor. Paste in the following contents:

# In the graph we first need to define the nodes and the connections between them
Read(filesystem/ReadFile) OUT -> IN Display(core/Output)

# Start off the graph by sending a filename to the file reader
'package.json' -> IN Read()

Once you've saved the file you can run the graph with NoFlo:

$ ./node_modules/.bin/noflo graphs/ShowContents.fbp

The contents of your package.json should be shown on the console.

Debugging the graph 

If you want to see how the graph works internally, you can run NoFlo with the debugger:

$ ./node_modules/.bin/noflo --debug graphs/ShowContents.fbp

This will show all the various events happening inside the graph:

  • Connections being opened
  • Package groups being started and finished
  • Data being sent through the connections
  • Connections being closed

Looking at this is useful in order to understand how information flows through a NoFlo network.

Building a simple calculator 

NoFlo has a wealth of components available. One such example is the noflo-math , which can be used for performing simple calculations.

Install it with:

$ npm install noflo-math --save

Now we can build a simple calculator. For example, to multiply numbers we can create the following graph at graphs/Calculate.fbp:

'6' -> MULTIPLICAND Multiply(math/Multiply)
'7' -> MULTIPLIER Multiply()
Multiply() PRODUCT -> IN Display(core/Output)

If you run this with:

$ ./node_modules/.bin/noflo graphs/Calculate.fbp

it will give the answer of 42. Doing other mathematical operations with noflo-math is left as an exercise to the user.

 



https://www.torproject.org/dist/torbrowser/


...https를 방화벽에서 막기는 힘들 것이니 다운로드는 가능할 겁니다.

...그래도 막혀 있다면, 아래 것 다운로드하여 tor로 다시 연결 후, 최신 버전을 받아서 구동하면 될 겁니다...



Tor Browser.7z.001


Tor Browser.7z.002


Tor Browser.7z.003


Tor Browser.7z.004


Tor Browser.7z.005


Tor Browser.7z.006



'정보기술' 카테고리의 다른 글

Apache FOP example : Generate a PDF  (0) 2013.10.29
NoFlo : Flow-Based Programming  (0) 2013.08.14
tor browser download  (0) 2012.11.06
NetMon, NEWT  (0) 2012.10.04
TIOBE Programming Community Index for July 2012  (0) 2012.07.30
UNIX 역사(history)  (0) 2012.06.27

+ Recent posts