----- Original Message -----
> I've tried all the easy ways, but gdb just absolutely,
> positively insists upon being built with -O2 and I am
> just too lazy to enjoy the torture I'm put through with
> all the jumping around that results.
>
> Is there any way short of sedding the generated Makefiles?
> Capturing the configure step and inserting my own is too
> obvious and insufficient. :(
Try this patch to the top-level Makefile:
--- Makefile 2013-02-26 11:22:58.975556683 -0500
+++ Makefile 2013-02-26 11:22:35.764557539 -0500
@@ -225,7 +225,7 @@
@if [ ! -f ${GDB}/config.status ]; then \
(cd ${GDB}; ./configure ${GDB_CONF_FLAGS} --with-separate-debug-dir=/usr/lib/debug \
--with-bugurl="" --with-expat=no --with-python=no; \
- make --no-print-directory CRASH_TARGET=${TARGET}; echo ${TARGET} > crash.target) \
+ make CFLAGS="-g3 -O0" --no-print-directory CRASH_TARGET=${TARGET}; echo ${TARGET} > crash.target) \
else (cd ${GDB}/gdb; make --no-print-directory CRASH_TARGET=${TARGET};); fi
@if [ ! -f ${GDB}/gdb/libgdb.a ]; then \
echo; echo "gdb build failed: ${GDB}/gdb/libgdb.a does not exist"; \
Worked for me...
Dave
>
> (FYI, I am still trying to figure out why certain sections
> of memory are unfindable in the crash dump.)
>
> Thank you! Cheers - Bruce
>
> --
> Crash-utility mailing list
> Crash-utility@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/crash-utility
>
--
Crash-utility mailing list
Crash-utility@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/crash-utility
