search for: ddebugging

Erik de Castro Lopo wrote: > When should FLAC__HAS_X86INTRIN be defined? What header file should I be > checking for? Ah, should be checking for <x86intrin.h>. The rest seems to be coming together. Testing this now. Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/

Hello, I try to recompile syslinux-4.00 pre31 on RHEL5 with gcc-4.1.2 and nasm 2.07. Because I'm looking for information about that gpxelinux->chain.c32 hd0 boot problem I added -DDEBUG=2 to com32/lib/Makefile I get: objdump -h pxelinux.elf > pxelinux.sec perl lstadjust.pl pxelinux.lsr pxelinux.sec pxelinux.lst objcopy -O binary pxelinux.elf pxelinux.raw ../lzo/prepcore

On Tue, Apr 14, 2015 at 03:20:08PM -0400, Gene Cumm wrote: > > I thought I would try to find out how pxelinux copes with this, by trying > > to insert printfs in pxe_init, but nothing gets printed. > > This is normal. Can you give me hint as to why setting > > DEBUGOPT = -DDEBUG=1 -DDEBUG_STDIO -DCORE_DEBUG=1 changes that state of normality? (AFAICT dprintf.h

> Speaking of CFLAGS, it looks like configure.in clobbers any existing > CFLAGS in > the environment. This can be a pain when trying to compile with a > modified > CFLAGS, as the usual idiom is: > > CFLAGS=... ./configure ... > > thus propagating CFLAGS to all generated makefiles. The right thing > to do is > probably to prepend to CFLAGS instead of replacing

I cannot compile the latest xen build (make world): make[4]: Entering directory `/setup/xen/xen-unstable/tools/firmware/acpi'' gcc -o acpigen -I. -I../../libxc acpi_build.c acpi_dsdt.c acpi_facs.c acpi_fadt. c acpi_gen.c acpi_madt.c acpi_rsdt.c acpi_gen.c: In function âmainâ: acpi_gen.c:44: warning: incompatible implicit declaration of built-in function â exitâ acpi_gen.c:51: warning:

I cannot compile the latest xen build (make world): make[4]: Entering directory `/setup/xen/xen-unstable/tools/firmware/acpi'' gcc -o acpigen -I. -I../../libxc acpi_build.c acpi_dsdt.c acpi_facs.c acpi_fadt. c acpi_gen.c acpi_madt.c acpi_rsdt.c acpi_gen.c: In function âmainâ: acpi_gen.c:44: warning: incompatible implicit declaration of built-in function â exitâ acpi_gen.c:51: warning:

Hi Everyone, We caught a report for a failed self test when using Clang 5.0 and 6.0 with -DDEBUG and -O1 (i.e., a "debug build"). The code is question is located at https://github.com/weidai11/cryptopp/blob/master/cham-simd.cpp . It is the SSSE3 code path for CHAM64. Other optimizations levels are OK for Clang. GCC, ICC and MSVC are OK. The code is valgrind, Sanitizer, Coverity and

I have reason to believe that an odd box that is having boot trouble has three instances of "!PXE" in the chunk of memory that "Method D" should look at. I thought I would try to find out how pxelinux copes with this, by trying to insert printfs in pxe_init, but nothing gets printed. I can spew lots of output if I set DEBUGOPT = -DDEBUG=1 -DDEBUG_STDIO -DCORE_DEBUG=1 but

The sed expression is wrong, any flags with '-g' in any position gets zapped, for example: -mfloat-gprs=double (for powerpc e500) -> -mfloatprs=double. Which gives build errors and is perfectly valid in real use scenarios to switch from e500v1 (single precision) code to e500v2 (double precision) code. Signed-off-by: Gustavo Zacarias <gustavo at zacarias.com.ar> ---

I have several related questions. 1. Is it possible to use a GUI: Rstudio/Eclipse/Visual-studio to debug compiled code on Windows? Things that work on Eclipse for Windows do not work on Eclipse for Windows. 2. R CMD INSTALL seems to override default attempts to provide CFLAGS="-DDEBUG -g3 -O0" 3. Is it necessary to compile R with debug turned on? One of the FAQs mentioned to

Hello everybody, A recent update of the sssd-common-2.8.1-1.el8.x86_64 package is causing sssd.service systemctl failures all over my CentosOS machines. What is the best way to report this issue and when can we expect an update from the sssd-common package for this regression bug? I think sssd-common is part of the baseos repository and installed even when the configuration file is not

Anyone else getting this when building the latest mesa? make[3]: Entering directory `/usr/local/nouveau/mesa2/mesa/src/gallium/targets/dri-nouveau' gcc -c -I. -I../../../../src/mesa/drivers/dri/common -Iserver -I../../../../include -I../../../../include/GL/internal -I../../../../src/mapi -I../../../../src/gallium/include -I../../../../src/gallium/auxiliary

...t variable... LANG=en_US export LANG error... LANG=C export LANG error... LANG=en_US LANGVAR=en_US export LANG export LANGVAR perl ./Makefile.PL Perl's config says that U32 access must be aligned. Writing Makefile for Digest::MD5 make gcc -c -D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS -DDEBUGGING -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm -O2 -g -pipe -march=i386 -mcpu=i686 -DVERSION=\"2.33\" -DXS_VERSION=\"2.33\" -fPIC "-I/usr/lib/perl5/5.8.0/i386-linux-thread-multi/CORE" -DU32_ALIGNMENT_REQUIRED...

...XS_Search__Xapian__WritableDatabase_allterms_end(PerlInterpreter*, CV*)': Xapian.c:1138: warning: 'RETVAL' may be used uninitialized in this function libtool: compile: g++ -c -I/localtemp/amit/rohit/FinalProj/xapian-core-1.2.5/include -D_REENTRANT -D_GNU_SOURCE -DPERL_USE_SAFE_PUTENV -DDEBUGGING -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -DVERSION=\"1.2.5.0\" -DXS_VERSION=\"1.2.5.0\" -...

Jan Stary wrote: > > if test "x$debug" = xtrue; then > > CPPFLAGS="-DDEBUG $CPPFLAGS" > > - CFLAGS=$(echo "$CFLAGS" | sed 's/-g//') > > - CFLAGS="-g $CFLAGS" > > + CFLAGS=$(echo "-g $CFLAGS") > > Just zap the sed line, and leave > > CFLAGS="-g $CFLAGS" > > there; no need to

Hello! I want to run windows in xen. My linux distrution in ubuntu 6.06 amd 64. I downloaded and installed xen 3.0.2 from binaries. I found that hvmloader is not included in binary distribution :-( So I try to compile it from sources. I get following error: cpp -P -DDEBUG -DTEXTADDR=0x000D0000 vmxassist.ld > vmxassist.tmp ld -o vmxassist -m elf_i386 -nostdlib --fatal-warnings -N -T

...me of which seem to change the API somewhat: "-DNETSNMP_ENABLE_IPV6 -O2 -march=i586 -mtune=i686 -fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -g -fno-strict-aliasing -fstack-protector-all -Ulinux -Dlinux=linux -I/usr/include/rpm -D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS -DDEBUGGING -fno-strict-aliasing -pipe -Wdeclaration-after-statement -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/lib/perl5/5.8.8/i586-linux-thread-multi/CORE -I. -I/usr/include" At any rate, things seem to be working. Thanks again. -- - Charles Lepple

I noticed several issues when diagnosing why pxechn.c32 didn't work in 5.01-pre3. 1) pxechn.c32, prdhcp.c32 and other modules crash Syslinux and force a reboot by executing an unresolved symbols. unload_pxe(), dns_resolv() and pxe_call() are the three. "Error: An undefined symbol was referenced" 2) In past versions, I built a debug build by having "CFLAGS += -DDEBUG=1"

On Fri, Jul 12, 2013 at 2:21 AM, H. Peter Anvin <hpa at zytor.com> wrote: > On 07/11/2013 10:16 PM, Raphael S.Carvalho wrote: >> This patch adds support for serial output functions. >> It may be useful for debugging purposes since you can separate ordinary outputs from debugging dumps. >> Just add "serial.h", and use either serial_print or serial_puts as you

I'm considering the suggestion which was raised before about turning the debugging messages on by default in isolinux, or specifically, not building the non-debugging-messages version in the standard distribution. What do people think (especially distro maintainers?) -hpa