FreeBSD Doc/books_developers-handbook — Portuguese (Brazil) @ Weblate: At the <command>gdb</command> prompt, type <userinput>break main</userinput>. This will tell …

Translation

Content

Source string comment (itstool) path: sect3/para

English

At the <command>gdb</command> prompt, type <userinput>break main</userinput>. This will tell the debugger to skip the preliminary set-up code in the program being run and to stop execution at the beginning of the program's code. Now type <userinput>run</userinput> to start the program— it will start at the beginning of the set-up code and then get stopped by the debugger when it calls <function>main()</function>.

Portuguese (Brazil)

620/4160

Needs editing

Context	English	Portuguese (Brazil)	State
	Start <command>lldb</command> locally and type the following command to connect to the remote server:
	(lldb) <userinput>gdb-remote <replaceable>host:port</replaceable></userinput>	(gdb) <userinput>attach <replaceable>pid</replaceable></userinput>
	<command>lldb-server</command> can also attach to a running process. To do that, type the following on the remote server:
	<prompt>%</prompt> <userinput>lldb-server g <replaceable>host:port</replaceable> --attach <replaceable>pid-or-name</replaceable></userinput>	<prompt>%</prompt> <userinput>comm -23 ../<replaceable>old</replaceable> ../<replaceable>new</replaceable></userinput>
	Using gdb
	Starting gdb
	Start up gdb by typing
	<prompt>%</prompt> <userinput>gdb <replaceable>progname</replaceable></userinput>	<prompt>%</prompt> <userinput>gdb <replaceable>progname</replaceable></userinput>
	although many people prefer to run it inside <application>Emacs</application>. To do this, type:	embora muitas pessoas prefiram correr dentro <application> Emacs </application> . Você pode fazer isso por:
	<userinput>M-x gdb RET <replaceable>progname</replaceable> RET</userinput>	<userinput>M-x gdb RET <replaceable>progname</replaceable> RET</userinput>
	Finally, for those finding its text-based command-prompt style off-putting, there is a graphical front-end for it (<package>devel/xxgdb</package>) in the Ports Collection.	Finalmente, se você achar que o estilo de prompt de comando baseado em texto é desagradável, há um front-end gráfico para ele ( <package> devel / xxgdb </package> ) na coleção de Portos
	Running a Program with gdb	Executando um programa no depurador
	Compile the program with <option>-g</option> to get the most out of using <command>gdb</command>. It will work without, but will only display the name of the function currently running, instead of the source code. A line like:	Você precisará ter compilado o programa com o <option value=-g> -g </option> opção para tirar o máximo proveito do uso <command> gdb </command> . Ele funcionará sem, mas você verá apenas o nome da função em que está, em vez do código-fonte. Se você vir uma linha como:
	… (no debugging symbols found) …	… (no debugging symbols found) …
	when <command>gdb</command> starts up means that the program was not compiled with <option>-g</option>.	quando <command> gdb </command> inicia, você saberá que o programa não foi compilado com o <option value=-g> -g </option> opção.
	At the <command>gdb</command> prompt, type <userinput>break main</userinput>. This will tell the debugger to skip the preliminary set-up code in the program being run and to stop execution at the beginning of the program's code. Now type <userinput>run</userinput> to start the program— it will start at the beginning of the set-up code and then get stopped by the debugger when it calls <function>main()</function>.	No <command> gdb </command> prompt, digite <userinput> quebrar principal </userinput> . Isso dirá ao depurador que você não está interessado em observar o código de configuração preliminar no programa que está sendo executado e que ele deve interromper a execução no início de seu código. Agora digite <userinput> corre </userinput> para iniciar o programa - ele será iniciado no início do código de configuração e, em seguida, será interrompido pelo depurador quando ele for chamado <function> a Principal() </function> . (Se você já se perguntou onde <function> a Principal() </function> é chamado, agora você sabe!).
	To step through the program a line at a time, press <command>n</command>. When at a function call, step into it by pressing <command>s</command>. Once in a function call, return from it by pressing <command>f</command>, or use <command>up</command> and <command>down</command> to take a quick look at the caller.	Agora você pode percorrer o programa, uma linha de cada vez, pressionando <command> n </command> . Se você chegar a uma chamada de função, poderá entrar nela pressionando <command> s </command> . Quando estiver em uma chamada de função, você pode retornar de uma chamada de função pressionando <command> f </command> . Você também pode usar <command> acima </command> e <command> baixa </command> para dar uma olhada rápida no chamador
	Here is a simple example of how to spot a mistake in a program with <command>gdb</command>. This is our program (with a deliberate mistake):	Aqui está um exemplo simples de como identificar um erro em um programa com <command> gdb </command> . Este é o nosso programa (com um erro deliberado):
	<prompt>%</prompt> <userinput>cc -g -o temp temp.c</userinput> <prompt>%</prompt> <userinput>./temp</userinput> This is my program anint = 4231	<prompt>%</prompt> <userinput>cc -g -o temp temp.c</userinput> <prompt>%</prompt> <userinput>./temp</userinput> This is my program anint = 4231
	That was not what we expected! Time to see what is going on!	Isso não foi o que esperávamos! Hora de ver o que está acontecendo!
	<prompt>%</prompt> <userinput>gdb temp</userinput> GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.13 (i386-unknown-freebsd), Copyright 1994 Free Software Foundation, Inc. (gdb) <userinput>break main</userinput> <lineannotation>Skip the set-up code</lineannotation> Breakpoint 1 at 0x160f: file temp.c, line 9. <lineannotation>gdb puts breakpoint at main()</lineannotation> (gdb) <userinput>run</userinput> <lineannotation>Run as far as main()</lineannotation> Starting program: /home/james/tmp/temp <lineannotation>Program starts running</lineannotation> Breakpoint 1, main () at temp.c:9 <lineannotation>gdb stops at main()</lineannotation> (gdb) <userinput>n</userinput> <lineannotation>Go to next line</lineannotation> This is my program <lineannotation>Program prints out</lineannotation> (gdb) <userinput>s</userinput> <lineannotation>step into bazz()</lineannotation> bazz (anint=4231) at temp.c:17 <lineannotation>gdb displays stack frame</lineannotation> (gdb)	<prompt>%</prompt> <userinput>gdb temp</userinput> GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.13 (i386-unknown-freebsd), Copyright 1994 Free Software Foundation, Inc. (gdb) <userinput>break main</userinput> <lineannotation>Skip the set-up code</lineannotation> Breakpoint 1 at 0x160f: file temp.c, line 9. <lineannotation>gdb puts breakpoint at main()</lineannotation> (gdb) <userinput>run</userinput> <lineannotation>Run as far as main()</lineannotation> Starting program: /home/james/tmp/temp <lineannotation>Program starts running</lineannotation> Breakpoint 1, main () at temp.c:9 <lineannotation>gdb stops at main()</lineannotation> (gdb) <userinput>n</userinput> <lineannotation>Go to next line</lineannotation> This is my program <lineannotation>Program prints out</lineannotation> (gdb) <userinput>s</userinput> <lineannotation>step into bazz()</lineannotation> bazz (anint=4231) at temp.c:17 <lineannotation>gdb displays stack frame</lineannotation> (gdb)
	Hang on a minute! How did <symbol>anint</symbol> get to be <literal>4231</literal>? Was it not set to <literal>5</literal> in <function>main()</function>? Let us move up to <function>main()</function> and have a look.	Espere um minuto! Como foi <symbol> não anint </symbol> chegar a ser <literal> 4231 </literal> ? Nós não definimos para sermos <literal> 5 </literal> dentro <function> a Principal() </function> ? Vamos subir para <function> a Principal() </function> e dê uma olhada.
	(gdb) <userinput>up</userinput> <lineannotation>Move up call stack</lineannotation> #1 0x1625 in main () at temp.c:11 <lineannotation>gdb displays stack frame</lineannotation> (gdb) <userinput>p i</userinput> <lineannotation>Show us the value of i</lineannotation> $1 = 4231 <lineannotation>gdb displays 4231</lineannotation>	(gdb) <userinput>up</userinput> <lineannotation>Move up call stack</lineannotation> #1 0x1625 in main () at temp.c:11 <lineannotation>gdb displays stack frame</lineannotation> (gdb) <userinput>p i</userinput> <lineannotation>Show us the value of i</lineannotation> $1 = 4231 <lineannotation>gdb displays 4231</lineannotation>
	but we left the <literal>i=5;</literal> line out. As we did not initialize <symbol>i</symbol>, it had whatever number happened to be in that area of memory when the program ran, which in this case happened to be <literal>4231</literal>.	mas deixamos o <literal> i = 5; </literal> line out. Como nós não inicializamos <symbol> Eu </symbol> , tinha qualquer número que estivesse naquela área de memória quando o programa rodava, o que neste caso aconteceu <literal> 4231 </literal>
	The <command>gdb</command> command displays the stack frame every time we go into or out of a function, even if we are using <command>up</command> and <command>down</command> to move around the call stack. This shows the name of the function and the values of its arguments, which helps us keep track of where we are and what is going on. (The stack is a storage area where the program stores information about the arguments passed to functions and where to go when it returns from a function call.)	<command> gdb </command> exibe o quadro da pilha toda vez que entramos ou saímos de uma função, mesmo se estivermos usando <command> acima </command> e <command> baixa </command> para percorrer a pilha de chamadas. Isso mostra o nome da função e os valores de seus argumentos, o que nos ajuda a saber onde estamos e o que está acontecendo. (A pilha é uma área de armazenamento onde o programa armazena informações sobre os argumentos passados às funções e para onde ir quando retorna de uma chamada de função).
	Examining a Core File with gdb	Examinando um arquivo principal
	To examine a core file, start up <command>gdb</command> in the usual way. Instead of typing <command>break</command> or <command>run</command>, type	Para examinar um arquivo principal, inicie <command> gdb </command> da maneira usual. Em vez de digitar <command> pausa </command> ou <command> corre </command> , tipo
	(gdb) <userinput>core <replaceable>progname</replaceable>.core</userinput>	(gdb) <userinput>core <replaceable>progname</replaceable>.core</userinput>
	If the core file is not in the current directory, type <userinput>dir /path/to/core/file</userinput> first.	Se você não está no mesmo diretório que o arquivo principal, você terá que fazer <userinput> dir / caminho / para / core / arquivo </userinput> primeiro.
	The debugger should display something like this:	Você deveria ver algo assim:
	<prompt>%</prompt> <userinput>gdb <filename><replaceable>progname</replaceable></filename></userinput> GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.13 (i386-unknown-freebsd), Copyright 1994 Free Software Foundation, Inc. (gdb) <userinput>core <filename><replaceable>progname</replaceable>.core</filename></userinput> Core was generated by `<filename><replaceable>progname</replaceable></filename>'. Program terminated with signal 11, Segmentation fault. Cannot access memory at address 0x7020796d. #0 0x164a in bazz (anint=0x5) at temp.c:17 (gdb)	<prompt>%</prompt> <userinput>gdb a.out</userinput> GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.13 (i386-unknown-freebsd), Copyright 1994 Free Software Foundation, Inc. (gdb) <userinput>core a.out.core</userinput> Core was generated by `a.out'. Program terminated with signal 11, Segmentation fault. Cannot access memory at address 0x7020796d. #0 0x164a in bazz (anint=0x5) at temp.c:17 (gdb)