Wiki Mageia

‎Step o: Verify new LocalSettings.php: 2025_03_28 codegazer added updated snippet from /etc/mediawiki/LocalSettings.php for moving from Mageia 8 to Mageia 9

← Older revision Revision as of 00:00, 29 March 2025 (2 intermediate revisions by the same user not shown)Line 3: Line 3:  This document describes steps for moving the content of a wiki from one server to another. This document describes steps for moving the content of a wiki from one server to another.  <br> <br> −This method has been tested moving a mediawiki (using mysql/mariadb and Apache) between Mageia 5 and Mageia 6 servers.+This method has been tested moving a mediawiki (using mysql/mariadb and Apache) between Mageia 5 and Mageia 6 servers (in 2017) and also between Mageia 8 and Mageia 9 servers (in 2025).     = Benefits = = Benefits = Line 633: Line 633:  The effect of this was that image files were not being displayed on the new server. The effect of this was that image files were not being displayed on the new server.    −I manually added the following snippet to the new server's /etc/mediawiki/LocalSettings.php and then the wiki content was presented correctly.+For the move between Mageia 5 and 6 in 2017 I manually added the following snippet to the new server's /etc/mediawiki/LocalSettings.php and then the wiki content was presented correctly.     <pre> <pre> Line 671: Line 671:     # END-OF-snippet from /etc/mediawiki/LocalSettings.php   # END-OF-snippet from /etc/mediawiki/LocalSettings.php    +</pre>  +  +For the move between Mageia 8 and 9 in 2025 I manually added the following snippet to the new server's /etc/mediawiki/LocalSettings.php and then the wiki content was presented correctly.  +  +<pre>  +# START-OF-snippet from /etc/mediawiki/LocalSettings.php follows:  +  +# End of automatically generated settings.  +# Add more configuration options below.  +  +##LOCAL - manually added extensions  +  +wfLoadExtension( 'Cite' );  +wfLoadExtension( 'Gadgets' );  +wfLoadExtension( 'ImageMap' );  +wfLoadExtension( 'InputBox' );  +wfLoadExtension( 'LocalisationUpdate' );  +wfLoadExtension( 'Nuke' );  +wfLoadExtension( 'ParserFunctions' );  +wfLoadExtension( 'Poem' );  +wfLoadExtension( 'Renameuser' );  +wfLoadExtension( 'SpamBlacklist' );  +wfLoadExtension( 'SyntaxHighlight_GeSHi' );  +wfLoadExtension( 'TitleBlacklist' );  +wfLoadExtension( 'WikiEditor' );  +  +# Add more configuration options below.  +  +$wgFileExtensions = array( 'png', 'gif', 'jpg', 'jpeg', 'doc',  +        'xls', 'mpp', 'pdf', 'ppt', 'tiff', 'bmp', 'docx', 'xlsx',  +        'pptx', 'ps', 'odt', 'ods', 'odp', 'odg', 'zip', 'txt',  +        'mp3', 'mp4', 'wmv'  +        );  +  +# END-OF-snippet from /etc/mediawiki/LocalSettings.php  +  </pre> </pre>    Line 809: Line 845:     # find wiki database name from wiki config # find wiki database name from wiki config −wgDBname=$(grep wgDBname ${wiki_conf} | grep -v "^#" | sed -e "s/^.//" | cut -d\" -f2)+wgDBname=$(grep "^.wgDBname" ${wiki_conf} | grep -v "^#" | sed -e "s/^.//" | cut -d\" -f2)     # find wiki user name from wiki config # find wiki user name from wiki config Codegazer

← Older revision Revision as of 20:35, 27 March 2025 Line 6: Line 6:  Wie du dir vorstellen kannst, sind wir von überall aus der Welt, weshalb es unmöglich ist um uns von Angesicht zu Angesicht zu treffen, aus diesem Grund verwenden wir IRC im Kanal [ircs://irc.libera.chat:6697/#mageia-qa #mageia-qa] auf Liberachat. Wie du dir vorstellen kannst, sind wir von überall aus der Welt, weshalb es unmöglich ist um uns von Angesicht zu Angesicht zu treffen, aus diesem Grund verwenden wir IRC im Kanal [ircs://irc.libera.chat:6697/#mageia-qa #mageia-qa] auf Liberachat.    −Wir halten dort jede Woche am Donnerstag. Meetings werden protokolliert mit Meetbot, welches Aktionen- und Info-Punkte, ähnlich zu normalen minütlichen Meetings. Protokolle von vorherigen  Meetings können [http://meetbot.mageia.org/mageia-qa/ hier] gefunden werden.  +Wir halten dort jeden ersten und dritten Donnerstag im Monat Meetings. Die Meetings werden ursprünglich mit Meetbot protokolliert, welches Aktionen- und Info-Punkte erstellt, ähnlich zu normal protokollierte Meetings. Protokolle der ursprünglichen Meetings können [http://meetbot.mageia.org/mageia-qa/ hier] gefunden werden.       Seit Juni 2021 werden unsere Meetings in [ircs://irc.libera.chat:6697/#mageia-meeting #mageia-meeting] abgehalten und unsere Protokolle sind [http://meetbot.mageia.org/mageia-meeting/ hier] verfügbar. Seit Juni 2021 werden unsere Meetings in [ircs://irc.libera.chat:6697/#mageia-meeting #mageia-meeting] abgehalten und unsere Protokolle sind [http://meetbot.mageia.org/mageia-meeting/ hier] verfügbar. Psyca

← Older revision Revision as of 20:28, 27 March 2025 Line 33: Line 33:  Das ist alles. Wirklich. Jemand wird Sie im Team willkommen heißen. Das meiste, was Sie wissen müssen um anzufangen, finden Sie bereits [[Your first steps in the QA team|hier in unserem Wiki]][[File:Flag-united-kingdom02.png|21px|link=]]. Das ist alles. Wirklich. Jemand wird Sie im Team willkommen heißen. Das meiste, was Sie wissen müssen um anzufangen, finden Sie bereits [[Your first steps in the QA team|hier in unserem Wiki]][[File:Flag-united-kingdom02.png|21px|link=]].    −Es ist auch sehr hilfreich wenn Sie zu uns in den irc://irc.libera.chat/#mageia-qa #mageia-qa Libera Chat] Kanal beitreten, wo Fragen schnell beantwortet werden können, und ein [[Sophie-de|Bot]] nützliche Informationen über die verschiedenen Pakete in Mageia zur Verfügung stellt. Hier werden auch jeden Donnerstag Meetings abgehalten.+Es ist auch sehr hilfreich wenn Sie zu uns in den irc://irc.libera.chat/#mageia-qa #mageia-qa Libera Chat] Kanal beitreten, wo Fragen schnell beantwortet werden können, und ein [[Sophie-de|Bot]] nützliche Informationen über die verschiedenen Pakete in Mageia zur Verfügung stellt. Hier werden auch jeden ersten und dritten Donnerstag im Monat Meetings abgehalten. Psyca

← Older revision Revision as of 23:03, 26 March 2025 Line 5: Line 5:  As you can imagine, we are from all over the world so it is impossible to actually meet face to face, so we meet using IRC at [ircs://irc.libera.chat:6697/#mageia-qa #mageia-qa] on Liberachat. As you can imagine, we are from all over the world so it is impossible to actually meet face to face, so we meet using IRC at [ircs://irc.libera.chat:6697/#mageia-qa #mageia-qa] on Liberachat.    −We hold meetings there each week on Thursdays. Meetings once were logged using a meetbot which can create action and info points similar to normal minuted meetings. Logs of the previous meetings can be found [http://meetbot.mageia.org/mageia-qa/ here].  +We hold meetings there on the first and third Thursdays of each month. Meetings once were logged using a meetbot which can create action and info points similar to normal minuted meetings. Logs of the previous meetings can be found [http://meetbot.mageia.org/mageia-qa/ here].       As of june 2021 our meetings have been moved to [ircs://irc.libera.chat:6697/#mageia-meeting #mageia-meeting] and the logs of those meetings can be found [http://meetbot.mageia.org/mageia-meeting/ here]. As of june 2021 our meetings have been moved to [ircs://irc.libera.chat:6697/#mageia-meeting #mageia-meeting] and the logs of those meetings can be found [http://meetbot.mageia.org/mageia-meeting/ here]. Tandrews16

← Older revision Revision as of 23:01, 26 March 2025 Line 35: Line 35:  * [[Your first steps in the QA team|Get involved!]] * [[Your first steps in the QA team|Get involved!]]    −That's it. Really. Somebody will then welcome you to the team. Most of what you need to know to get started is already [[Your first steps in the QA team|here on the wiki]]. It is useful if you can also join us [irc://irc.libera.chat/#mageia-qa #mageia-qa on Libera Chat] where questions can be quickly answered, and [[Sophie|a bot]] can provide useful information on the various Mageia packages. Also, meetings are held there every Thursday.+That's it. Really. Somebody will then welcome you to the team. Most of what you need to know to get started is already [[Your first steps in the QA team|here on the wiki]]. It is useful if you can also join us [irc://irc.libera.chat/#mageia-qa #mageia-qa on Libera Chat] where questions can be quickly answered, and [[Sophie|a bot]] can provide useful information on the various Mageia packages. Also, meetings are held there on the first and third Thursdays of the month. Tandrews16

← Older revision Revision as of 22:57, 26 March 2025 Line 26: Line 26:       −Please try to attend the weekly team meetings which take place [irc://irc.libera.chat/#mageia-qa on IRC] in #mageia-qa on irc.libera.chat every Thursday+Please try to attend the team meetings which take place [irc://irc.libera.chat/#mageia-qa on IRC] in #mageia-qa on irc.libera.chat on the first and third Thursdays of the month.       Tandrews16

‎xsltproc: Fix link again

← Older revision Revision as of 17:21, 20 March 2025 (2 intermediate revisions by the same user not shown)Line 69: Line 69:  https://bugs.mageia.org/show_bug.cgi?id=20760 https://bugs.mageia.org/show_bug.cgi?id=20760    −xsltproc can be tested by following the instructions [http://www.w3schools.com/xsl/xsl_transformation.asp here] and creating cdcatalog.xml and cdcatalog.xsl as below:+xsltproc can be tested by following the instructions [https://www.w3schools.com/xml/ref_xsl_el_transform.asp here] and creating cdcatalog.xml and cdcatalog.xsl as below:       Line 87: Line 87:       −There is an extended version you can [http://www.w3schools.com/xsl/cdcatalog.xml download from here] - right click & save link as.+There is an extended version you can [https://www.w3schools.com/xml/cdcatalog.xml download from here] - right click & save link as.    −The xsl stylesheet should be saved as cdcatalog.xsl as below. [http://www.w3schools.com/xsl/cdcatalog.xsl direct download here].  +The xsl stylesheet should be saved as cdcatalog.xsl as below. [https://www.w3schools.com/xml/cdcatalog.xsl direct download here].         Line 144: Line 144:     </pre> </pre> −  −      == python-libxslt == == python-libxslt == Katnatek

‎xsltproc: Other link update

← Older revision Revision as of 16:59, 20 March 2025 (One intermediate revision by the same user not shown)Line 69: Line 69:  https://bugs.mageia.org/show_bug.cgi?id=20760 https://bugs.mageia.org/show_bug.cgi?id=20760    −xsltproc can be tested by following the instructions [http://www.w3schools.com/xsl/xsl_transformation.asp here] and creating cdcatalog.xml and cdcatalog.xsl as below:+xsltproc can be tested by following the instructions [https://www.w3schools.com/xml/ref_xsl_el_transform.asp here] and creating cdcatalog.xml and cdcatalog.xsl as below:       Line 89: Line 89:  There is an extended version you can [http://www.w3schools.com/xsl/cdcatalog.xml download from here] - right click & save link as. There is an extended version you can [http://www.w3schools.com/xsl/cdcatalog.xml download from here] - right click & save link as.    −The xsl stylesheet should be saved as cdcatalog.xsl as below. [http://www.w3schools.com/xsl/cdcatalog.xsl direct download here].  +The xsl stylesheet should be saved as cdcatalog.xsl as below. [https://www.w3schools.com/xml/cdcatalog.xsl direct download here].         Line 144: Line 144:     </pre> </pre> −  −      == python-libxslt == == python-libxslt == Katnatek

← Older revision Revision as of 18:05, 19 March 2025 Line 71: Line 71:  Overview: Overview:    −# Developer builds a package SRPM containing all application source code as well as any unpackaged dependency source code needed by the application (i.e. vendoring it), including a SBOM for those dependencies+# Developer builds a package SRPM containing all application source code as well as any unpackaged dependency source code needed by the application (i.e. vendoring it), including a SBOM (Software Bill of Materials) for those dependencies  # The build system uses only locally-available source to build (as always) and adds a reference to the main source(s) to the SBOM, for completeness # The build system uses only locally-available source to build (as always) and adds a reference to the main source(s) to the SBOM, for completeness  # For interpreted languages, the build system puts any vendored code into a filesystem location specific to the application in the final RPM # For interpreted languages, the build system puts any vendored code into a filesystem location specific to the application in the final RPM Barjac

← Older revision Revision as of 08:25, 19 March 2025 Line 14: Line 14:  * [[:Category:Policies|Mageia Richtlinien]] * [[:Category:Policies|Mageia Richtlinien]]  * [[Packagers linkpage|Externe Links]] [[File:Flag-united-kingdom02.png|21px|link=]] * [[Packagers linkpage|Externe Links]] [[File:Flag-united-kingdom02.png|21px|link=]] −* [[Mandriva_packagers|Mandriva Paketbauer]] [[File:Flag-united-kingdom02.png|21px|link=]]+* [[Mandriva_packagers|Mageia Paketbauer]] [[File:Flag-united-kingdom02.png|21px|link=]]     |style="-moz-border-radius:10px; width:48%; background: #F6F6F6;"| '''Kommunikationswege für Paketbauer''' |style="-moz-border-radius:10px; width:48%; background: #F6F6F6;"| '''Kommunikationswege für Paketbauer''' Psyca

← Older revision Revision as of 18:15, 18 March 2025 (2 intermediate revisions by the same user not shown)Line 13: Line 13:  * [[Packagers groups]] * [[Packagers groups]]  * [[Packagers linkpage|External links]] * [[Packagers linkpage|External links]] −* [[Mandriva_packagers|Mandriva packagers]]+* [[Mandriva_packagers|Mageia packagers]]     |style="-moz-border-radius:10px; width:48%; background: #F6F6F6;"| '''Packagers communication''' |style="-moz-border-radius:10px; width:48%; background: #F6F6F6;"| '''Packagers communication''' Mokraemer

Add example commit, more details

← Older revision Revision as of 18:36, 17 March 2025 Line 2: Line 2:     * take a checkout of puppet configuration * take a checkout of puppet configuration −* go to modules/buildsystem/templates+* go to ''modules/buildsystem/templates'' −* edit submit-todo.conf+* edit ''submit-todo.conf''    −in checks/version/cauldron ( yaml hierarchy )+in ''checks/version/cauldron'' ( yaml hierarchy )     * change mode from   * change mode from   Line 13: Line 13:     * commit and push * commit and push −* connect on valstar and apply puppet manifest+   +The change will come into effect on the next Puppet run (up to 45 minutes). Here is [https://gitweb.mageia.org/infrastructure/puppet/commit/?id=7827863672e52cfdf43d20a7d776cc1ba6ec313a an example] of such a commit.  +   +A Release Freeze is done similarly, but with  +   + mode: freeze     == How to add someone to the list of users able to upload == == How to add someone to the list of users able to upload ==    −* connect on ldap.mageia.org with sysadmin account+* add the user to the group ''mga-release_managers'' using the [[SOP Adding user to group]] procedure −* add the user to the group "mga-release_managers"      [[Category:Sysadmin]] [[Category:Sysadmin]] Danf

Removed sparkleshare

← Older revision Revision as of 14:29, 17 March 2025 Line 618: Line 618:     The category contains the following packages, alphabetically: The category contains the following packages, alphabetically: −*+* sparkleshare     <!-- More? --> <!-- More? --> Papoteur

Atualização do link depuração de falha de software

← Older revision Revision as of 02:49, 15 March 2025 Line 209: Line 209:  *[[As_easy_as_a_shell|Tão fácil quanto um shell]] *[[As_easy_as_a_shell|Tão fácil quanto um shell]]  *[[Cauldron]] *[[Cauldron]] −*[[Debugging software crashes|Depuração de falhas de software]]+*[[Depuração_de_falhas_de_software-pt-BR|Depuração de falhas de software]]  *[[Display Managers|<span style="color:green;">Gerenciadores de exibição</span>]] *[[Display Managers|<span style="color:green;">Gerenciadores de exibição</span>]]  *[[Drakcowsay|<span style="color:green;">Drakcowsay</span>]] *[[Drakcowsay|<span style="color:green;">Drakcowsay</span>]] Xgrind

Add pt-BR

← Older revision Revision as of 02:43, 15 March 2025 Line 5: Line 5:  [[Category:Triage]] [[Category:Triage]]    −{{Multi language banner-fr|[[Fehlersuche_bei_Softwareabstürze-de|Deutsch]] ; [[Debugging software crashes|English]] ; [[Débogage de plantage de logiciel-fr|français]] ;}}+{{Multi language banner-fr|[[Fehlersuche_bei_Softwareabstürze-de|Deutsch]] ; [[Debugging software crashes|English]] ; [[Débogage de plantage de logiciel-fr|français]] ; [[Depuração de falhas de software-pt-BR|Português brasileiro]] ;}}     {{introduction-fr|Cette page est conçue pour vous aider à collecter des informations pertinentes en cas de plantage d’une application et doit éventuellement être corrigée par vous-même.}} {{introduction-fr|Cette page est conçue pour vous aider à collecter des informations pertinentes en cas de plantage d’une application et doit éventuellement être corrigée par vous-même.}} Xgrind

Add pt-BR

← Older revision Revision as of 02:43, 15 March 2025 Line 5: Line 5:  [[Category:Triage]] [[Category:Triage]]    −{{multi language banner|[[Fehlersuche_bei_Softwareabstürze-de|Deutsch]] ; [[Debugging software crashes|English]] ; [[Débogage de plantage de logiciel-fr|français]] ;}}+{{multi language banner|[[Fehlersuche_bei_Softwareabstürze-de|Deutsch]] ; [[Debugging software crashes|English]] ; [[Débogage de plantage de logiciel-fr|français]] ; [[Depuração de falhas de software-pt-BR|Português brasileiro]] ;}}     {{introduction|This page is intended to help you gather useful information when you encounter a software crash, and maybe fixing it by yourself.}} {{introduction|This page is intended to help you gather useful information when you encounter a software crash, and maybe fixing it by yourself.}} Xgrind

Add pt-BR

← Older revision Revision as of 02:42, 15 March 2025 Line 5: Line 5:  [[Category:Triage]] [[Category:Triage]]    −{{Multi_language_banner-de|[[Fehlersuche_bei_Softwareabstürze-de|Deutsch]] ; [[Debugging_software_crashes|English]] ; [[Débogage de plantage de logiciel-fr|français]] ;}}+{{Multi_language_banner-de|[[Fehlersuche_bei_Softwareabstürze-de|Deutsch]] ; [[Debugging_software_crashes|English]] ; [[Débogage de plantage de logiciel-fr|français]] ; [[Depuração de falhas de software-pt-BR|Português brasileiro]] ;}}  {{mgaport-de|url=Fehlersuche_bei_Softwareabstuerzen}} {{mgaport-de|url=Fehlersuche_bei_Softwareabstuerzen}}    Xgrind

Criando a página Depuração de falhas de software-pt-BR

New page

[[Category:Bugsquad]]
[[Category:Documentation ]]
[[Category:Howtos]]
[[Category:Packaging]]
[[Category:Triage]]

{{multi language banner-pt-BR|[[Fehlersuche_bei_Softwareabstürze-de|Deutsch]] ; [[Debugging software crashes|English]] ; [[Débogage de plantage de logiciel-fr|français]] ; [[Depuração de falhas de software-pt-BR|Português brasileiro]] ;}}

{{introduction-pt-BR|Esta página tem como objetivo ajudar você a reunir informações úteis quando ocorrer uma falha de software e talvez consertá-la sozinho.}}

== Preliminares ==

Primeiro, você deve instalar os pacotes ''-debug'' dos aplicativos e todas as bibliotecas que podem estar envolvidas. Isso permitirá que todas as ferramentas de depuração relatem informações mais úteis.

O próprio gdb lhe dará a linha de comando para executar a fim de instalar esses pacotes '''-debug''' e reiniciar o {{cmd-pt-BR|gdb}}.
Agora você pode começar a coletar informações úteis usando as várias ferramentas listadas abaixo.

Para poder instalar pacotes -debug, você precisa adicionar ou habilitar os repositórios -debug separados. Se você adicionou um conjunto completo de repositórios via gerenciamento de software Mageia, tudo o que você precisa fazer é atualizá-los com o seguinte comando em um terminal como root:
{{command-pt-BR|urpmi.update --no-ignore debug|prompt=#}}

== gdb ==

O programa gdb é o depurador GNU. Quando um programa trava devido a uma falha de segmentação ou um aborto, o gdb permitirá que você obtenha um backtrace, que é o lugar no programa onde o erro ocorreu.

=== Executando sua aplicação dentro do gdb ===

Se você puder reproduzir a falha facilmente, poderá executar seu aplicativo dentro do gdb e obter informações úteis quando a falha ocorrer.

* Inicie o gdb informando o caminho para seu aplicativo e diga para ele ser executado, se necessário, com os parâmetros.

{{output-pt-BR|gdb /bin/cat}}{{withbr|<nowiki>GNU gdb 6.3-7mdv2007.0 (Mandriva Linux release 2007.0)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or 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.
This GDB was configured as "x86_64-mandriva-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".

(gdb)run /proc
Starting program: /bin/cat /proc
/bin/cat: /proc: Is a directory

Program exited with code 01.
(gdb)</nowiki>}}{{stop}}

* Se você receber mensagens sobre o sinal 33, você precisa dizer ao gdb para não parar nelas e passá-las para o aplicativo e, em seguida, reinicá-lo:

{{pre-pt-BR|<nowiki>Program received signal SIG33, Real-time event 33.
[Switching to Thread 1182845264 (LWP 11543)]
0x00002b661d87d536 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
(gdb) handle SIG33 nostop noprint noignore pass
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) kill
Kill the program being debugged? (y or n) y
(gdb) run</nowiki>}}

* Quando o programa falhar, você receberá um prompt de gdb. Obter o backtrace com o comando {{Cmd-pt-BR|bt full}}. Esta é a informação necessária no relatório de bugs. Se as mensagens anteriores falarem sobre tópicos, você deve obter todos os backtraces com {{Cmd-pt-BR|thread apply all bt full}}.

{{pre-pt-BR|<nowiki>(gdb) bt full
#0 0x00002b526953c7ef in poll () from /lib64/libc.so.6
No symbol table info available.
#1 0x00002b52691f412e in g_main_context_iterate (context=0x51f2d0, block=1, dispatch=1,
self=Variable "self" is not available.) at gc:2977
max_priority = 2147483647
timeout = 30000
some_ready = Variable "some_ready" is not available.</nowiki>}}

=== Executando o gdb em um arquivo principal ===

Se por algum motivo você não conseguir reproduzir facilmente a falha dentro do gdb, mas tiver um arquivo principal, poderá fazer uma análise post-mortem. Por exemplo

{{command-pt-BR|gdb /bin/cat core.42}}

então, obtenha o backtrace com

{{Cmd-pt-BR|thread apply all bt full}}

(Se nenhum núcleo é gerado após uma segfault, tente executar {{Cmd-pt-BR|ulimit -c unlimited}} no shell a partir do qual você vai iniciar o seu aplicativo).

=== Anexando o gdb a um aplicativo em execução ===

Depurar aplicativos com startups complexas, por exemplo, serviços de sistema, pode ser complicado, pois você pode não conhecer todos os parâmetros usados com o binário quando é lançado.

Nesses casos (assumindo que a falha não ocorra durante a inicialização), você pode anexar gdb a uma instância em execução do aplicativo.

Primeiro, identificar o processo em que a colisão ocorrerá, por exemplo, com

{{cmd-pt-BR|ps ax {{!}} grep //nome do aplicativo//}}. Se o aplicativo estiver executando vários processos, tente notá-los todos, causando a falha e verificando o syslog para ver quais deles realmente falharam; quando você reiniciar o aplicativo, você pode anexar o gdb ao processo que ocupa o mesmo lugar relativo na lista.

Em seguida, anexar o gdb ao processo usando

{{cmd-pt-BR|gdb nome-do-executável id-do-processo}}

Isso fará com que o Gdb anexe a esse processo e o suspenda. Para retomar sua execução, use o comando
gdb {{cmd-pt-BR|c}}.

Finalmente, cause o acidente, o que resultará em gdb informando sobre isso e colocando um prompt, no qual você pode solicitar um backtrace.

Se você tiver que executar o gdb de um tty, canalize a saída para um arquivo de texto (para que você possa anexá-lo a um relatório de bugs mais tarde). Isso pode ser feito usando o comando {{cmd-pt-BR|tee}}, por exemplo:

{{cmd-pt-BR|gdb /bin/cat 2>&1 {{!}} tee logfile.txt}}

Isso salvará toda a saída para o logfile.txt. Quando você terminar, o arquivo de saída terá um registro de sua sessão de gdb.

=== Depuração do Apache no Mageia 2 ===

Depurar o apache tornou-se problemático na Mageia 2. O script abaixo deve ser útil.

{{pre-pt-BR|<nowiki>#!/bin/bash

# debugging apache got broken with systemd in mga2, it used to be as easy as:
# "/etc/rc.d/init.d/httpd stop; /etc/rc.d/init.d/httpd debug"
# this script should do the trick.
# Oden Eriksson <oeriksson@mandriva.com>

/etc/rc.d/init.d/httpd stop
defines=`/etc/rc.d/init.d/httpd show_defines`
gdb /usr/sbin/httpd --batch --quiet -ex "run -f /etc/httpd/conf/httpd.conf -DNO_DETACH -DONE_PROCESS -DDEBUG $defines" -ex "thread apply all bt full" -ex "quit"</nowiki>}}

== strace ==

O programa strace listará todas as chamadas do sistema feitas pelo aplicativo (abra um arquivo, leia em um soquete de rede, ...) e isso pode ajudar a encontrar alguns problemas, como um arquivo ausente, um diretório não escredável... etc

Você pode executá-lo com

{{cmd-pt-BR|strace -f -o \\arquivo-de-saida\\ \\comando\\}}

por exemplo

{{cmd-pt-BR|strace -f -o ls.strace ls /tmp}}

executará {{cmd-pt-BR|ls /tmp}} e salvar todas as chamadas do sistema para o arquivo ls.strace

== ltrace ==

== valgrind ==

Quando um programa é executado sob a supervisão de Valgrind, todas as leituras e gravações de memória são verificadas, e chamadas para malloc/new/free/delete são interceptadas. Como resultado, o Valgrind pode detectar problemas como:

* Utilização de memória não inicializada
* Ler/escrever a memória após de ter sido libertada
* Ler/escrever fora do final dos blocos malloc'd
* Ler/escrever áreas inapropriadas na pilha
* Vazamentos de memória - onde ponteiros para blocos malc'd são perdidos para sempre
* Passar de memória não-inicializada e/ou não endereçável às chamadas do sistema
* Uso incompatível de malloc/novo/novo [] vs livre/excluir/excluir []

[[Bugsquad_Portal|Ir para o Portal Bugsquad]] Xgrind

← Older revision Revision as of 12:48, 14 March 2025 Line 276: Line 276:     {{Bug|33330}} - '''aegisub stürzt beim Starten in eine wayland Session ab. - WORKAROUND:''' Starten Sie diese von der Befehlszeile über folgenden Befehl: {{cmd|<nowiki>env GDK_BACKEND=x11 aegisub</nowiki>}}. {{Bug|33330}} - '''aegisub stürzt beim Starten in eine wayland Session ab. - WORKAROUND:''' Starten Sie diese von der Befehlszeile über folgenden Befehl: {{cmd|<nowiki>env GDK_BACKEND=x11 aegisub</nowiki>}}.  +  +'''BEHOBEN DURCH EINE AKTUALISIERUNG''' {{Bug|33366}} -  Nach dem Ausführen von '''neochat''' in einer leichtgewichtigen Desktop-Umgebung, kann keine neue Sitzung gestartet werden, bis Sie die Anwendung über das Symbol in der Taskleiste schließen. Dieses Problem wurde durch eine Aktualisierung behoben, jedoch, wenn Sie bereits auf dieses Problem gestoßen waren, können Sie weiterhin keine neue Sitzung starten. Wir hoffen, dass Sie Ihre Accountdaten kennen, da Sie die Verzeichnisse {{folder|~/.local/share/KDE/neochat}}, {{file|~/.config/neochatrc}}, {{file|~/.config/KDE/neochat.conf}}, {{folder|~/.cache/KDE/neochat}} löschen müssen.  +  +Auch wenn Sie einen Passwortmanager bevorzugen, ({{prog|gnome-keyring}} , {{prog|kwalletmanager}}, {{prog|keepassxc}}), installieren Sie die Aktualisierung vor der Nutzung der Anwendung. Für [https://bugs.mageia.org/show_bug.cgi?id=32712#c18 kwallet] und keepassxc müssen Sie noch ein paar Einstellungen durchführen.     {{Bug|33697}} - '''Nextcloud Client''' - Wir schaffen es nicht dieses aktuell zu halten. Verwenden Sie stattdessen das AppImage über den Upstream - siehe [[Nextcloud-client]]. {{Bug|33697}} - '''Nextcloud Client''' - Wir schaffen es nicht dieses aktuell zu halten. Verwenden Sie stattdessen das AppImage über den Upstream - siehe [[Nextcloud-client]]. Psyca

‎Various software: Use folder template in folders

← Older revision Revision as of 17:50, 13 March 2025 Line 359: Line 359:  {{Bug|33330}} - '''aegisub crashes at start in wayland session. - WORKAROUND:''' Start it from command line this way: {{cmd|<nowiki>env GDK_BACKEND=x11 aegisub</nowiki>}}.   {{Bug|33330}} - '''aegisub crashes at start in wayland session. - WORKAROUND:''' Start it from command line this way: {{cmd|<nowiki>env GDK_BACKEND=x11 aegisub</nowiki>}}.      −'''FIXED BY UPDATE''' {{Bug|33366}} -  After first run '''neochat''' in light desktops can't start a new session once you quit from application icon in taskbar. It is fixed in the update, but if you already bite by this you note still can't start a new session, I hope you have your account data because you need to remove {{file|~/.local/share/KDE/neochat}}, {{file|~/.config/neochatrc}}, {{file|~/.config/KDE/neochat.conf}}, {{file|~/.cache/KDE/neochat}}.+'''FIXED BY UPDATE''' {{Bug|33366}} -  After first run '''neochat''' in light desktops can't start a new session once you quit from application icon in taskbar. It is fixed in the update, but if you already bite by this you note still can't start a new session, I hope you have your account data because you need to remove {{folder|~/.local/share/KDE/neochat}}, {{file|~/.config/neochatrc}}, {{file|~/.config/KDE/neochat.conf}}, {{folder|~/.cache/KDE/neochat}}.     Also if you have some preference in password manager application ({{prog|gnome-keyring}} , {{prog|kwalletmanager}}, {{prog|keepassxc}}) please install before the update and for [https://bugs.mageia.org/show_bug.cgi?id=32712#c18 kwallet] and keepassxc you have to make some configurations. Also if you have some preference in password manager application ({{prog|gnome-keyring}} , {{prog|kwalletmanager}}, {{prog|keepassxc}}) please install before the update and for [https://bugs.mageia.org/show_bug.cgi?id=32712#c18 kwallet] and keepassxc you have to make some configurations. Katnatek