Why icc-compiled executable has no debugging symbols found though with -g option


Why icc-compiled executable  has no debugging symbols found as below. But gcc-compiled executable has.


$ icc -g a.c

$ gdb a.out

GNU gdb (GDB) Red Hat Enterprise Linux (7.0.1-23.el5)

Copyright (C) 2009 Free Software Foundation, Inc.

License GPLv3+: GNU GPL version 3 or later <>

This is free software: you are free to change and redistribute it.

There is NO WARRANTY, to the extent permitted by law.  Type "show copying"

Win32/x64 checking current executable??

I have a test program that I use to test all of the calls in my DLL app.

Currently, this is a Win32 program calling a Win32 DLL - all good.

I now want to use the same code, built as x64 to test the x64 version of my DLL, and so I need the program to be able to detect whether it was built as Win32 or x64.  I have been using GetBinaryType from Kernel32 - this correctly detects whether a program (exe or DLL) is 32 or 64 bit, but only when called from a Win32 build.

How can I call GetBinaryType properly from an x64 build?

I'm using



В предыдущей статье я рассказал об Intel® VT-x и расширениях данной технологии для увеличения эффективности виртуализации. В этой статье я расскажу о том, что предлагается тем, кому готов сделать ещё один шаг: запускать ВМ внутри ВМ — вложенная виртуализация.


В предыдущей статье я рассказал о трёх режимах IA-32: защищённом, VM86 и SMM. Хотя их и не принято связывать с виртуализацией, они служат для создания изолированных окружений для программ, исполняемых на процессоре. В этой статье я опишу «настоящую» технологию виртуализации Intel® VT-x. Я хочу показать, как теория эффективной виртуализации проявляется в каждом аспекте её практической реализации.

SEI are out of order

I'm adding user_data_registered_itu_t_t35 SEI messages during an H.264 encoding, and the SEI messages are being stored in the bitstream in the display order instead of encoding order.  The encoder is set to accept frames in display order, and the encoded frames are being encoded correctly.  

Shouldn't the SEI messages associated with each frame also be in display order?    Tracked the problem by adding a sequence byte to each SEI buffer, and the sequence increases for each SEI NAL.

Any idea on what I might be doing wrong?

Q about passing array boundaries or sizes

Suppose I have this:

integer x(100)

call xprint(x(23:70) )


subroutine xprint(x)

integer x(*)

end subroutine

Normally I would have to ALSO tell it how many elements of X to print.

But I was wondering if there is a subroutine call that would actually tell me how many elements I am passing?

UBOUND and SIZEOF do not work here. I get a compiler error.

Subscribe to Developers