The C99 [`stdint.h`](http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/stdint.h.html) defines these:

- `int8_t`
- `int16_t`
- `int32_t`
- `uint8_t`
- `uint16_t`
- `uint32_t`

And, if the architecture supports them:

- `int64_t`
- `uint64_t`

There are various other integer typedefs in `stdint.h` as well.

If you&#39;re stuck without a C99 environment then you should probably supply your own typedefs and use the C99 ones anyway.

The `uint32` and `uint64` (i.e. without the `_t` suffix) are probably application specific.

Those integer types are all defined in `stdint.h`

If you are using C99 just include `stdint.h`. BTW, the 64bit types are there iff the processor supports them.

The questioner actually asked about int16 (etc) rather than (ugly) int16_t (etc).

There are no standard headers - nor any in Linux&#39;s /usr/include/ folder that define them without the &quot;_t&quot;.

  

I&#39;ve seen several posts for this issue but didn&#39;t found my solution.

I&#39;m trying to serve static files within my Django 1.3 development environment.

Here are my settings

    ...
    STATIC_ROOT = &#39;/home/glide/Documents/django/cbox/static/&#39;
    STATIC_URL = &#39;/static/&#39;
    STATICFILES_DIRS = (
      &#39;/static/&#39;,
    )
    ...

My urls.py

    urlpatterns = patterns(&#39;&#39;,
    ...
      url(r&#39;^static/(?P&lt;path&gt;.*)$&#39;, &#39;django.views.static.serve&#39;,
        {&#39;document_root&#39;, settings.STATIC_ROOT}
      ),
    ...
    );

My _/home/glide/Documents/django/cbox/static/_ directory is like

    css
      main.css
    javascript
    image

I get a 404 error when trying to access _http://127.0.0.1:8000/static/css/main.css_.

Do I have to specify patterns for css, javascript and images individually ?

Django - Static file not found

I am getting following error in my SQL server 2008 R2 database:

&gt; Cannot use a `CONTAINS` or `FREETEXT` predicate on table or indexed view &#39;tblArmy&#39; because it is not full-text indexed.



Cannot use a CONTAINS or FREETEXT predicate on table or indexed view because it is not full-text indexed

I often see source code using types like uint32, uint64 and I wonder if they should be defined by the programmer in the application code or if they are defined in a standard lib header.

What&#39;s the best way to have these types on my application source code?


Are types like uint32, int32, uint64, int64 defined in any stdlib header?

<p>I often see source code using types like uint32, uint64 and I wonder if they should be defined by the programmer in the application code or if they are defined in a standard lib header.</p>
<p>What's the best way to have these types on my application source code?</p>


Any portable code that uses bitfields seems to distinguish between little- and big-endian platforms. See the [declaration of struct iphdr in linux kernel](http://lxr.linux.no/#linux+v2.6.38/include/linux/ip.h) for an example of such code. I fail to understand why bit endianness is an issue at all.

As far as I understand, bitfields are purely compiler constructs, used to facilitate bit level manipulations.

For instance, consider the following bitfield:
&lt;code&gt;&lt;pre&gt;
struct ParsedInt {
    unsigned int f1:1;
    unsigned int f2:3;
    unsigned int f3:4;
};
uint8_t i;
struct ParsedInt *d = &amp;i;
&lt;/pre&gt;&lt;/code&gt;
Here, writing &lt;code&gt;d-&gt;f2&lt;/code&gt; is simply a compact and readable way of saying &lt;code&gt;(i&gt;&gt;1) &amp;  (1&lt;&lt;4 - 1)&lt;/code&gt;.

However, bit operations are well-defined and work regardless of the architecture. So, how come bitfields are not portable?

Why bit endianness is an issue in bitfields?

 - In simple terms what are pts and dts values?
 - Why are they important while transcoding [decode-encode] videos ?

What does this code bit do in [**ffmpeg.c**][1] , what is its purpose?

    01562    ist-&gt;next_pts = ist-&gt;pts = picture.best_effort_timestamp;
    01563    if (ist-&gt;st-&gt;codec-&gt;time_base.num != 0) {
    01564        int ticks= ist-&gt;st-&gt;parser ? ist-&gt;st-&gt;parser-&gt;repeat_pict+1 : ist-&gt;st-&gt;codec-&gt;ticks_per_frame;
    01565        ist-&gt;next_pts += ((int64_t)AV_TIME_BASE *
    01566                         ist-&gt;st-&gt;codec-&gt;time_base.num * ticks) /
    01567                         ist-&gt;st-&gt;codec-&gt;time_base.den;
    01568    }


  [1]: http://cekirdek.pardus.org.tr/~ismail/ffmpeg-docs/ffmpeg_8c-source.html

ffmpeg.c what are pts and dts ? what does this code block do in ffmpeg.c?

&gt; **Possible Duplicate:**  
&gt; [Does free(ptr) where ptr is NULL corrupt memory?](https://stackoverflow.com/questions/1938735/does-freeptr-where-ptr-is-null-corrupt-memory)  

&lt;!-- End of automatically inserted text --&gt;

I&#39;m writing a C function that frees a pointer if it was `malloc()`ed. The pointer can either be NULL (in the case that an error occured and the code didn&#39;t get the chance to allocate anything) or allocated with `malloc()`. Is it safe to use `free(ptr);` instead of `if (ptr != NULL) free(ptr);`?

`gcc` doesn&#39;t complain at all, even with `-Wall -Wextra -ansi -pedantic`, but is it good practice?

Is it good practice to free a NULL pointer in C?

Got the following error when I tried to compile a C application in 64-bit FreeBSD:

&gt; relocation R_X86_64_32S can not be used when making a shared object; recompile with -fPIC

What is `R_X86_64_32S` relocation and what is `R_X86_64_64`?

I&#39;ve googled about the error, and it&#39;s possible causes - It&#39;d be great if anyone could tell what R_X86_64_32S really means.


What do R_X86_64_32S and R_X86_64_64 relocation mean?

I recently ran into [an issue][1] that could easily be solved using modulus division, but the input was a float:

&gt; Given a periodic function (e.g. `sin`) and a computer function that can only compute it within the period range (e.g. [-π, π]), make a function that can handle any input.

The &quot;obvious&quot; solution is something like:

    #include &lt;cmath&gt;

    float sin(float x){
        return limited_sin((x + M_PI) % (2 *M_PI) - M_PI);
    }

Why doesn&#39;t this work? I get this error:

 &lt;!-- language: lang-none --&gt;

    error: invalid operands of types double and double to binary operator %

Interestingly, it does work in Python:

 &lt;!-- language: lang-python --&gt;

    def sin(x):
        return limited_sin((x + math.pi) % (2 * math.pi) - math.pi)

 [1]: https://stackoverflow.com/questions/6091837/sin-and-cos-are-slow-is-there-an-alternatve/6091846#6091846

Why does modulus division (%) only work with integers?

I have grown accustomed to `strtod` and variants.
I am wondering why there is no `strtoi` shipped with `&lt;stdlib.h&gt;`.
Why is it that the integer type is left out of this party?

Specifically I am asking why there is not a version of `atoi` with the safety features of `strtod`?

Why is there no strtoi in stdlib.h?

Is snprintf always null terminating the destination buffer?

In other words, is this sufficient:

    char dst[10];

    snprintf(dst, sizeof (dst), &quot;blah %s&quot;, somestr);

or do you have to do like this, if somestr is long enough?

    char dst[10];

    somestr[sizeof (dst) - 1] = &#39;\0&#39;;
    snprintf(dst, sizeof (dst) - 1, &quot;blah %s&quot;, somestr);


I am interested both in what the standard says and what some popular libc might do which is not standard behavior.



Is snprintf() ALWAYS null terminating?

**Short version of question:**
How can I get gdb to use the debugging symbols for `libc`?

**Longer version:**
I am debugging a program with gdb and I want to see information about a futex used by `libc`. However, at some point during debugging I get output such as:

    Catchpoint 2 (call to syscall futex), 0x00007ffff772b73e in ?? () from /lib/libc.so.6
    (gdb) bt
    #0  0x00007ffff772b73e in ?? () from /lib/libc.so.6
    #1  0x00007ffff767fb90 in ?? () from /lib/libc.so.6
    #2  0x00007ffff767a4c0 in vfprintf () from /lib/libc.so.6
    #3  0x00007ffff768565a in printf () from /lib/libc.so.6
    ....

When I run `info sharedlibrary` in gdb at the breakpoint I see:

    (gdb) info sharedlibrary
    From                To                  Syms Read   Shared Object Library
    0x00007ffff7dddaf0  0x00007ffff7df6704  Yes (*)     /lib64/ld-linux-x86-64.so.2
    0x00007ffff7bc53e0  0x00007ffff7bd1388  Yes (*)     /lib/libpthread.so.0
    0x00007ffff79ba190  0x00007ffff79bd7d8  Yes (*)     /lib/librt.so.1
    0x00007ffff76538c0  0x00007ffff7766c60  Yes (*)     /lib/libc.so.6
    0x00007ffff6c1fd80  0x00007ffff6c303c8  Yes (*)     /lib/libgcc_s.so.1
    (*): Shared library is missing debugging information.

And when I run `ldd` I see:

	linux-vdso.so.1 =&gt;  (0x00007ffff7fde000)
	libpthread.so.0 =&gt; /lib/libpthread.so.0 (0x00007ffff7dbf000)
	librt.so.1 =&gt; /lib/librt.so.1 (0x00007ffff7bb6000)
	libc.so.6 =&gt; /lib/libc.so.6 (0x00007ffff7833000)
	/lib64/ld-linux-x86-64.so.2 (0x00007ffff7fdf000)

I am using Ubuntu 10.04 and I think that the version of `libc` with debug symbols is in `/usr/lib/debug/lib`.  I tried setting my `LD_LIBRARY_PATH` variable to have this at the front of the path but that did not seem to make a difference.

I&#39;m not completely clear on how the program chooses which shared libraries to load, whether this is set at runtime or compile time (I sort of assumed runtime but now I&#39;m not sure).  So information on how to get gdb to use the debug version of `libc` is appreciated.


How to use debug version of libc

A student asked the question and I didn&#39;t know for sure.  

Guesses include: &quot;counted&quot;, &quot;clearing&quot;, &quot;chunked&quot;, &quot;complete&quot;, ...

The standard library documentation doesn&#39;t say what it stands for and there aren&#39;t similarly named functions that would indicate a pattern.  Does anyone know the actual etymology and perhaps have an authoritative reference to back it up?

Content Type	Original Author	Original Content on Stackoverflow
Question	philix	View Question on Stackoverflow
Solution 1 - C	mu is too short	View Answer on Stackoverflow
Solution 2 - C	GWW	View Answer on Stackoverflow
Solution 3 - C	BiGYaN	View Answer on Stackoverflow
Solution 4 - C	Steve	View Answer on Stackoverflow

Are types like uint32, int32, uint64, int64 defined in any stdlib header?

C Problem Overview

C Solutions

Solution 1 - C

Solution 2 - C

Solution 3 - C

Solution 4 - C

Cannot use a CONTAINS or FREETEXT predicate on table or indexed view because it is not full-text indexed

Django - Static file not found

Attributions