Can you suggest a better forum to post?


 
Thread Tools Search this Thread
Contact Us Post Here to Contact Site Administrators and Moderators Can you suggest a better forum to post?
# 1  
Old 03-07-2017
Can you suggest a better forum to post?

Hello!

I posted twice on issues I'm having getting the latest GCC compiler to compile ( "Command failed for target 'check-recursive' error" in the Solaris forum and "Compiling GCC 6.3.0 - Error with Library" in the UNIX for Beginners... forum) with zero responses. After many hours of beating my head against the wall trying to resolve the issues I'm encountering, I'm looking for any help or suggestions that I can get. But, I think that perhaps I'm posting in the wrong forums. I would like to get responses & suggestions as quickly as possible as I'm swiftly getting behind schedule. Can you suggest which forum might be the best to post in for problems with compiling on a Sun server with Solaris 10?

Thanks for your help!
Have a terrific Tuesday!!
PJ Smilie
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. What is on Your Mind?

Inserting Attached Files into a Forum Post

OFF_TOPIC Hey ozsavran, Thanks for the great post and photo attachments. Do you mind to explain to me what steps you took to upload and attach those files? I cannot do it and want to attach files like you did. Thanks! (2 Replies)
Discussion started by: Neo
2 Replies

2. UNIX for Dummies Questions & Answers

This forum is closed for new thread ... post here.

This forum is closed for new threads. Please post in this forum: UNIX for Beginners Questions & Answers (0 Replies)
Discussion started by: Neo
0 Replies

3. Post Here to Contact Site Administrators and Moderators

Do I post to Homework forum if learning on own

Quick question, I'm learning shell scripting on my own from resources like the 'Teach Yourself' books, web sites, etc. If I have any questions about these materials, do I still need to post them to the homework section? The template asks specific things like school associated with or... (7 Replies)
Discussion started by: Chasman78
7 Replies

4. Post Here to Contact Site Administrators and Moderators

kindly reconsider my post in shell & scripting forum

Hi, this is regarding my post "ksh: how to extract strings from each line based on a condition" . Its not a home work or an assigment. I actually work in retail domain. The data I handle is very complex and confidential.So I can't divulge the actual patterns. In order to explain my problem, I have... (1 Reply)
Discussion started by: angie1234
1 Replies

5. Post Here to Contact Site Administrators and Moderators

Not getting any option to post a Forum

Hi All, can anybody suggest, what steps i should follow to post a forum, i am able to post a thread, and also my account is registered. thanks in advance (2 Replies)
Discussion started by: varunksharma87
2 Replies

6. Post Here to Contact Site Administrators and Moderators

forum to post availability for work?

Hello. Is there a forum to post my availability for work? (1 Reply)
Discussion started by: douglaskbell
1 Replies

7. Post Here to Contact Site Administrators and Moderators

How do I post UNIX questions in the forum

I guess this is the way I post questions then. (1 Reply)
Discussion started by: kwokang
1 Replies
Login or Register to Ask a Question
ERROR::SDT(7stap)														 ERROR::SDT(7stap)

NAME
error::sdt - <sys/sdt.h> marker failures DESCRIPTION
Systemtap's <sys/sdt.h> probes are modeled after the dtrace USDT API, but are implemented differently. They leave a only a NOP instruction in the userspace program's text segment, and add an ELF note to the binary with metadata. This metadata describes the marker's name and parameters. This encoding is designed to be parseable by multiple tools (not just systemtap: GDB, the GNU Debugger, also contains sup- port). These allow the tools to find parameters and their types, wherever they happen to reside, even without DWARF debuginfo. The reason finding parameters is tricky is because the STAP_PROBE / DTRACE_PROBE markers store an assembly language expression for each op- erand, as a result of use of gcc inline-assembly directives. The compiler is given a broad gcc operand constraint string ("nor") for the operands, which usually works well. Usually, it does not force the compiler to load the parameters into or out of registers, which would slow down an instrumented program. However, some instrumentation sites with some parameters do not work well with the default "nor" con- straint. unresolveable at run-time GCC may emit strings that an assembler could resolve (from the context of compiling the original program), but a run-time tool can- not. For example, the operand string might refer to a label of a local symbol that is not emitted into the ELF object file at all, which leaves no trace for the run-time. Reference to such parameters from within systemtap can result in "SDT asm not understood" errors. too complicated expression GCC might synthesize very complicated assembly addressing modes from complex C data types / pointer expressions. systemtap or gdb may not be able to parse some valid but complicated expressions. Reference to such parameters from within systemtap can result in "SDT asm not understood" errors. overly restrictive constraint GCC might not be able to even compile the original program with the default "nor" constraint due to shortage of registers or other reasons. A compile-time gcc error such as "asm operand has impossible constraints" may result. There are two general workarounds to this family of problems. change the constraints While compiling the original instrumented program, set the STAP_SDT_ARG_CONSTRAINT macro to different constraint strings. See the GCC manual about various options. For example, on many machine architectures, "r" forces operands into registers, and "g" leaves operands essentially unconstrained. revert to debuginfo As long as the instrumented program compiles, it may be fine simply to keep using <sys/sdt.h> but eschew extraction of a few indi- vidual parameters. In the worst case, disable <sys/sdt.h> macros entirely to eschew the compiled-in instrumentation. If DWARF debuginfo was generated and preserved, a systemtap script could refer to the underlying source context variables instead of the positional STAP_PROBE parameters. SEE ALSO
stap(1), stapprobes(3stap), error::dwarf(7stap), http://gcc.gnu.org/onlinedocs/gcc/Constraints.html, http://sourceware.org/systemtap/wiki/UserSpaceProbeImplementation, error::reporting(7stap) ERROR::SDT(7stap)