12-17-2010
Thanks for quick and useful reply!!
I actually just figured out the issue by rigorously debugging with print* commands.
I was searching for x within a list x1, x2, x3...xn, but did not account for x<x1. D'oh! So despite executing without an issue, the result would have been garbage. I think you hit the nail on the head, I had no idea this could happen!
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello, sorry if this has been posted before but i was wondering if there is a way to run a program until a segmentation fault is found.
Currently i'm using a simple shell script which runs my program 100 times, sleeps 1 second because srand(time(0)) is dependent on seconds. Is there a possible... (1 Reply)
Discussion started by: aslambilal
1 Replies
2. Programming
After allocating memory for some variables, segfault is often to happen, due to the same reason: Address 0x1cd00000103 out of bounds
It is welcome to recommend some treatments. Thanks
e.g.
is_done = 0x1cd00000103 <Address 0x1cd00000103 out of bounds>,
hood = 0x23c00000247,
c =... (11 Replies)
Discussion started by: cdbug
11 Replies
3. Solaris
We have a Solaris 8 server which users login to via VNC to get a desktop. On that desktop these users use Netscape Communicator 4.9 to access a very important mail account. Unfortunately Netscape has started segfaulting regularly.
Does anyone have any ideas how I can try to find out what point... (1 Reply)
Discussion started by: aussieos
1 Replies
4. Programming
1. Even if i have the handles for ctrl+c it gives off a segfault
2. syslog doesn't log LOG_ERR event with log masked specified or non specified, it logs LOG_WARNING however...
#include <sys/types.h> /* include this before any other sys headers */
#include <sys/stat.h>
#include <fcntl.h>... (2 Replies)
Discussion started by: james2432
2 Replies
5. Programming
Hello everyone,
I'm writing a program using the id3lib unfortunately I've encountered with memory issue that cause segmentation fault. I tried to rerun and analyze the program with valgrind but it doesn't point me anywhere. I really stuck on this one.
Valgrind output:
==14716== Invalid read of... (2 Replies)
Discussion started by: errb
2 Replies
6. Programming
I have a program that allows users to specify the debug log file location and name.
I have tried using the access() and stat() but they both segfault if the drive say (d:\) is invalid. Both seem to be fine if the drive exists.
Could someone please point me in the direction to a function that... (1 Reply)
Discussion started by: robfwauk
1 Replies
7. Programming
GNU insight debugger is not available now a days and it is required to debug/inspect
assembly code as written in the book Assembly Language Programming step by step in Linux so my question is; is there any alternative to insight that I can use instead of insight in which I can get the same... (5 Replies)
Discussion started by: vectrum
5 Replies
8. Programming
hello all,
my question is not about How code can be rewritten, i just wanna know even though i am not using read only memory of C (i have declared str) why this function gives me segfault :wall:and the other code executes comfortably though both code uses same pointer arithmetic.
... (4 Replies)
Discussion started by: zius_oram
4 Replies
9. Programming
I am populating an array of string and print it.
But it going in infinite loop and causing segfault.
char Name = {
"yahoo",
"rediff",
"facebook",
NULL
};
main(int argc, char* argv)
{
int j = 0;
... (7 Replies)
Discussion started by: rupeshkp728
7 Replies
10. Programming
Another project, another bump in the road and another chance to learn. I've been trying to open gzipped files and parse data from them and hit a snag. I have data in gzips with a place followed by an ip or ip range sort of like this:
Some place:x.x.x.x-x.x.x.x
I was able to modify some code... (6 Replies)
Discussion started by: Azrael
6 Replies
GHI(1) General Commands Manual GHI(1)
NAME
ghi - command-line interface to the GitHub Issues API
SYNOPSIS
ghi command [arguments] [options]
DESCRIPTION
This manual page documents briefly the ghi command.
ghi is a command-line interface to the GitHub Issues API. It can be used to access all of GitHub's documented Issues API (v2) functionality
from the command line: open, close and manipulate issues.
If no command is given, the default action is list. If a number is given instead, the default action is show.
COMMANDS
list [ -s open|closed|all ]
Show open, closed or all issues (choose with -s, see below). Default is open.
show number
Show issue number. This command can be invoked also as ghi <number>.
open [ number ], o [ number ]
Create a new issue, and launch $EDITOR. If number is given, reopens that issue.
open -m message, o -m message
Create a new issue with message content (optionally, use
for new lines; first line will be the issue title).
close number, c number
Closes issue number.
edit number, e number
Edit issue number with $EDITOR.
label add|remove label number
Add or remove label to/from issue number.
You can use al or rl instead of, respectively, label add and label remove.
search term, s term
Search for term.
comment number, m number
Create a comment for issue number (with $EDITOR).
OPTIONS
-h, --help
Show summary of options.
-v, --verbose
Show issue details (only for show, list and search commands). Default is false.
-V, --version
Show program's version number and exit.
-s STATE, --state=STATE
Specify state (only for list and search (except "all") commands). Choices are: open (o), closed (c), all (a). Default is open.
-r REPO, --repo=REPO, --repository=REPO
Specify a repository. The format: "user/repo" or just "repo" (latter will get the user from the global git config).
-w, --web, --webbrowser
Show issue(s) GitHub page in web browser (only for list and show commands). Default is false.
AUTHOR
github-cli was written by Sander Smits <jhmsmits@gmail.com>.
This manual page was written by David Paleino <dapal@debian.org>, for the Debian project (and may be used by others).
April 13, 2010 GHI(1)