Sponsored Content
Top Forums Programming C++ Execution Inspection - Ideas Wanted Post 302771850 by ejr2122 on Thursday 21st of February 2013 07:40:47 PM
Old 02-21-2013
C++ Execution Inspection - Ideas Wanted

"C++ Execution Inspection" is the best term I could coin for what it is I'd like to do. Suggestions from anyone who has done programming in C++ on Linux are welcome.

I was taught C++ in classrooms that used MS Visual Studio a few years ago. Visual Studio had a debugging mode that made it really easy to keep track of what all my variables where at a given break point. Because of this, I was able to figure out what my code was doing rapidly. Now I'm looking for advice on how to achieve the same thing on Linux.

I've got two books on vim and am *trying* to become savvy with it. So far I like the way one can navigate in vi. Supposedly it is supposed to be stellar for programmers. Has anyone been able to achieve the kind of debugging I'm describing from within vim?

FOSS, it's unix like OSes, and command line tools are thing I put a lot of faith in. However, I don't have much experience using them for C++ development. As such, I'm looking for solutions that don't involve clunky IDEs, non-FOSS, MS Windows etc...

C++ is my favorite language. I have friends who like Clojure, Ruby, and many more who like Java. While I'm mildly aware of the cool features these languages have, they don't seem as intuitive to me as C and C++. A common gripe for these two languages are that they both use pointers, which seem to confuse some people. Personally, I think pointers are super cool.
 

4 More Discussions You Might Find Interesting

1. Programming

Help wanted

Hi, I know very little about C and Unix. I have written a program to use threads. The program needs to get some values from a very large database. I wrote a simple program and compiled but got the following errors..... cc mythread.c -lthread "/usr/include/pthread.h", line 120:... (3 Replies)
Discussion started by: reddyb
3 Replies

2. Shell Programming and Scripting

Expect Issue Serial Forground Execution vs Concurrent Background Execution

I have an expect script that interrogates several hundred unix servers for both access and directories therein using "ssh user@host ls -l /path". The combination of host/path are unique but the host may be interrogated multiple times if there are multiple paths to test. The expect script is run... (2 Replies)
Discussion started by: twk
2 Replies

3. What is on Your Mind?

Just wanted to say thanks!!!

Greetings all!! Have only recently signed up to this forum and I must say I am thoroughly impressed! :D Everyone has been nothing but amazingly helpful and I haven't been made to feel like the newbie that I am. I will definately be becoming a daily user of this site not only for help... (1 Reply)
Discussion started by: U_C_Dispatj
1 Replies

4. UNIX and Linux Applications

Need ideas for graduation project based on unix or linux Need ideas for graduation project based on

Dear all, i am in last year of electronics department in engineering faculty i need suggestions for a graduation project based on unix or free bsd or linux and electronics "embedded linux " i think about embedded unix for example or device drivers please i need helps (1 Reply)
Discussion started by: MOHA-1
1 Replies
PTHREAD_RWLOCK_UNLOCK(3P)				     POSIX Programmer's Manual					 PTHREAD_RWLOCK_UNLOCK(3P)

PROLOG
This manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (consult the correspond- ing Linux manual page for details of Linux behavior), or the interface may not be implemented on Linux. NAME
pthread_rwlock_unlock - unlock a read-write lock object SYNOPSIS
#include <pthread.h> int pthread_rwlock_unlock(pthread_rwlock_t *rwlock); DESCRIPTION
The pthread_rwlock_unlock() function shall release a lock held on the read-write lock object referenced by rwlock. Results are undefined if the read-write lock rwlock is not held by the calling thread. If this function is called to release a read lock from the read-write lock object and there are other read locks currently held on this read-write lock object, the read-write lock object remains in the read locked state. If this function releases the last read lock for this read-write lock object, the read-write lock object shall be put in the unlocked state with no owners. If this function is called to release a write lock for this read-write lock object, the read-write lock object shall be put in the unlocked state. If there are threads blocked on the lock when it becomes available, the scheduling policy shall determine which thread(s) shall acquire the lock. If the Thread Execution Scheduling option is supported, when threads executing with the scheduling policies SCHED_FIFO, SCHED_RR, or SCHED_SPORADIC are waiting on the lock, they shall acquire the lock in priority order when the lock becomes available. For equal priority threads, write locks shall take precedence over read locks. If the Thread Execution Scheduling option is not supported, it is implementa- tion-defined whether write locks take precedence over read locks. Results are undefined if any of these functions are called with an uninitialized read-write lock. RETURN VALUE
If successful, the pthread_rwlock_unlock() function shall return zero; otherwise, an error number shall be returned to indicate the error. ERRORS
The pthread_rwlock_unlock() function may fail if: EINVAL The value specified by rwlock does not refer to an initialized read-write lock object. EPERM The current thread does not hold a lock on the read-write lock. The pthread_rwlock_unlock() function shall not return an error code of [EINTR]. The following sections are informative. EXAMPLES
None. APPLICATION USAGE
None. RATIONALE
None. FUTURE DIRECTIONS
None. SEE ALSO
pthread_rwlock_destroy(), pthread_rwlock_rdlock(), pthread_rwlock_timedrdlock(), pthread_rwlock_timedwrlock(), pthread_rwlock_tryrdlock(), pthread_rwlock_trywrlock(), pthread_rwlock_wrlock(), the Base Definitions volume of IEEE Std 1003.1-2001, <pthread.h> COPYRIGHT
Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1, 2003 Edition, Standard for Information Technol- ogy -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2003 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html . IEEE
/The Open Group 2003 PTHREAD_RWLOCK_UNLOCK(3P)
All times are GMT -4. The time now is 02:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy