DevTools:Program Crash - Revision history

Refdoc: Refdoc moved page DevTools:Program crash to DevTools:Program Crash

2018-01-08T21:57:55Z

Refdoc moved page DevTools:Program crash to DevTools:Program Crash

Refdoc: Refdoc moved page Program crashing to DevTools:Program crash

2018-01-08T21:55:13Z

Refdoc moved page Program crashing to DevTools:Program crash

David Haslam: Category:Support

2009-12-04T14:54:39Z

Category:Support

Dmsmith: linked to osis2mod page

2008-09-09T20:13:53Z

linked to osis2mod page

Dmsmith: Sword -> SWORD

2008-09-02T16:48:12Z

Sword -> SWORD

Osk: grammar/capitalization

2008-01-30T09:24:19Z

grammar/capitalization

Skc: How to produce usefull informations about the crash

2008-01-30T09:05:12Z

How to produce usefull informations about the crash

New page

You're using a tool from sword to work on a module like <code>osis2mod</code> and it crash, displaying '<code>Segmentation fault (core dumped)</code>',

# run <code>ldd</code> on your binary (<code>ldd /usr/bin/osis2mod</code>) and post the output. Use '<code>type osis2mod</code>' if you don't know where <code>osis2mod</code> is installed.
# run the program with <code>strace</code> to reproduce the problem (<CODE>strace -o /tmp/osis2mod.strace osis2mod [arg1] [...]</code>). Don't post the output file (<code>/tmp/osis2mod.strace</code>) in the list as it will probably huge, but use an free online service (like http://pastebin.com/ or if you can read french http://dl.free.fr/. This file will display any system call and answer, allowing us to see I/O errors and things like that.
# run the program with <code>gdb</code>:
<blockquote><blockquote>
<code>gdb osis2mod</code><br/>
(gdb is starting)<br/>
<code>run [arg1] [....]</code><br/>
(wait until it crash)<br/>
<code>bt</code>
</blockquote></blockquote>
it will produce a backtrace of the stack, allowing us to see where it crash. Just post the backtrace (bt output) on the list.

If your program is never ending and output file does not grow (you suspect an endless loop), do the same, but in strace and gdb, hit Ctrl-C to stop it after a few seconds.

← Older revision		Revision as of 14:54, 4 December 2009
Line 14:		Line 14:

	If your program is never ending and an output file does not grow (you suspect an endless loop), do the same, but in strace and gdb, hit Ctrl-C to stop it after a few seconds.		If your program is never ending and an output file does not grow (you suspect an endless loop), do the same, but in strace and gdb, hit Ctrl-C to stop it after a few seconds.
		+
		+	[[Category:Support]]

← Older revision		Revision as of 20:13, 9 September 2008
Line 1:		Line 1:
−	If, while using a tool from SWORD to work on a module like <code>osis2mod</code>, it crashs, displaying '<code>Segmentation fault (core dumped)</code>',	+	If, while using a tool from SWORD to work on a module like <code>[[osis2mod]]</code>, it crashs, displaying '<code>Segmentation fault (core dumped)</code>',

	# Run <code>ldd</code> on your binary (<code>ldd /usr/bin/osis2mod</code>) and post the output. Use '<code>type osis2mod</code>' if you don't know where <code>osis2mod</code> is installed.		# Run <code>ldd</code> on your binary (<code>ldd /usr/bin/osis2mod</code>) and post the output. Use '<code>type osis2mod</code>' if you don't know where <code>osis2mod</code> is installed.

← Older revision		Revision as of 16:48, 2 September 2008
Line 1:		Line 1:
−	If, while using a tool from ~~Sword~~ to work on a module like <code>osis2mod</code>, it crashs, displaying '<code>Segmentation fault (core dumped)</code>',	+	If, while using a tool from SWORD to work on a module like <code>osis2mod</code>, it crashs, displaying '<code>Segmentation fault (core dumped)</code>',

	# Run <code>ldd</code> on your binary (<code>ldd /usr/bin/osis2mod</code>) and post the output. Use '<code>type osis2mod</code>' if you don't know where <code>osis2mod</code> is installed.		# Run <code>ldd</code> on your binary (<code>ldd /usr/bin/osis2mod</code>) and post the output. Use '<code>type osis2mod</code>' if you don't know where <code>osis2mod</code> is installed.

← Older revision	Revision as of 21:57, 8 January 2018
(No difference)

← Older revision	Revision as of 21:55, 8 January 2018
(No difference)

@@ Line 1: / Line 1: @@
-You're using a tool from sword to work on a module like <code>osis2mod</code> and it crash, displaying '<code>Segmentation fault (core dumped)</code>',
+If, while using a tool from Sword to work on a module like <code>osis2mod</code>, it crashs, displaying '<code>Segmentation fault (core dumped)</code>',
-# run <code>ldd</code> on your binary (<code>ldd /usr/bin/osis2mod</code>) and post the output. Use '<code>type osis2mod</code>' if you don't know where <code>osis2mod</code> is installed.
+# Run <code>ldd</code> on your binary (<code>ldd /usr/bin/osis2mod</code>) and post the output. Use '<code>type osis2mod</code>' if you don't know where <code>osis2mod</code> is installed.
-# run the program with <code>strace</code> to reproduce the problem (<CODE>strace -o /tmp/osis2mod.strace osis2mod [arg1] [...]</code>).  Don't post the output file (<code>/tmp/osis2mod.strace</code>) in the list as it will probably huge, but use an free online service (like http://pastebin.com/ or if you can read french http://dl.free.fr/.  This file will display any system call and answer, allowing us to see I/O errors and things like that.
+# Run the program with <code>strace</code> to reproduce the problem (<code>strace -o /tmp/osis2mod.strace osis2mod [arg1] [...]</code>).  Don't post the output file (<code>/tmp/osis2mod.strace</code>) in the list as it will probably be huge, but use a free online service (like http://pastebin.com/ or if you can read french http://dl.free.fr/).  This file will display any system call and answer, allowing us to see I/O errors and things like that.
-# run the program with <code>gdb</code>:
+# Run the program with <code>gdb</code>:
 <blockquote><blockquote>
          <code>gdb osis2mod</code><br/>
@@ Line 11: / Line 11: @@
          <code>bt</code>
 </blockquote></blockquote>
-it will produce a backtrace of the stack, allowing us to see where it crash. Just post the backtrace (bt output) on the list.
+It will produce a backtrace of the stack, allowing us to see where it crashed. Just post the backtrace (bt output) on the list.
-If your program is never ending and output file does not grow (you suspect an endless loop), do the same, but in strace and gdb, hit Ctrl-C to stop it after a few seconds.
+If your program is never ending and an output file does not grow (you suspect an endless loop), do the same, but in strace and gdb, hit Ctrl-C to stop it after a few seconds.