From caedd92eef8fe47c3925c12d8e81be911556b38b Mon Sep 17 00:00:00 2001 From: Tom Willemsen Date: Fri, 11 Jan 2013 01:16:41 +0100 Subject: Update files --- ...minated_with_signal_255_0_minutes_0_seconds.org | 39 ---------------------- 1 file changed, 39 deletions(-) delete mode 100644 site/blog/code-blocks_process_terminated_with_signal_255_0_minutes_0_seconds.org (limited to 'site/blog/code-blocks_process_terminated_with_signal_255_0_minutes_0_seconds.org') diff --git a/site/blog/code-blocks_process_terminated_with_signal_255_0_minutes_0_seconds.org b/site/blog/code-blocks_process_terminated_with_signal_255_0_minutes_0_seconds.org deleted file mode 100644 index 163e24e..0000000 --- a/site/blog/code-blocks_process_terminated_with_signal_255_0_minutes_0_seconds.org +++ /dev/null @@ -1,39 +0,0 @@ -#+TITLE: Code::Blocks "process terminted with signal 255 (0 minutes, 0 seconds)" -#+DATE: 2009-08-25 10:40 -#+TAGS: codeblocks fedora coding - -Yesterday after I came home from work I thought I'd try working on a -project I've been working on this past weekend. - -I was away from home this weekend, so all the work I'd done had been -on another computer, in a virtual Ubuntu installation, so I hadn't yet -tried it at home. - -Trying to build it went fine. Running it from a terminal went -fine. Even compiling and running on another Ubuntu installation (my -work laptop, non-virtual) went fine, but Code::Blocks reported to me -that whenever I tried running my application on my Fedora 11 home -installation that it terminated with signal 255. - -I couldn't find what was wrong, I knew the application worked since I -tested it in another terminal window and if I debugged it it'd go -great up to the point where it met with a ~cin~ or ~cout~. - -Being tired from a really long day (getting up at 5:00am, get on train -at 6:25am, get off train at 8:30am and at work 8:50am), I gave up -fairly quickly. - -This morning though the itch got worse and I just had to investigate -further. - -After about a minute of looking around I found someone at the Ubuntu -Forums asking about the exact same thing and it turns out that the -problem was that xterm wasn't installed. So a simple - -#+BEGIN_SRC sh - su -c "yum install xterm" -#+END_SRC - -was enough to fix the problem. - -Now I can start developing my application again! -- cgit v1.2.3-54-g00ecf