-
|
Hello ! For now, I have this launch.json configuration: {
"name": "Debug",
"type": "gdb",
"request": "attach",
"executable": "${workspaceFolder}/x86/hello_world.bin",
"target": "localhost:1234",
"remote": true,
"stopAtEntry": true,
"cwd": "${workspaceRoot}",
"debugger_args": ["-ix", "${workspaceFolder}/gdbinit"],
"gdbpath": "/opt/toolchains/i686-linux_6.4.0/bin/i686-linux-gdb",
"printCalls": true,
"showDevDebugOutput": true
}Qemu launch script: #!/bin/bash
qemu/i386-softmmu/qemu-system-i386 $1 -s \
-M pc -cpu Haswell -bios qemu/coreboot.rom \
-serial mon:stdio \
-m 256 \
-netdev user,id=n0,tftp=. \
-device e1000e,netdev=n0,mac=00:01:29:53:97:BA \
-nographic Logs: Why it doesn't work ? |
Beta Was this translation helpful? Give feedback.
Answered by
GitMensch
Mar 20, 2024
Replies: 2 comments 2 replies
-
|
The biggest part is likely this line:
So the GDB you use cannot understand the binary you told it to debug. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Anyway, if that helps, here's the makefile (I didn't write it, it was provided): ##########################################################################
#############
# Toolchain #
#############
TOOL_PREFIX := i686-linux
AR = $(TOOL_PREFIX)-ar
LD = $(TOOL_PREFIX)-ld
AS = $(TOOL_PREFIX)-as
CC = $(TOOL_PREFIX)-gcc
OBJCOPY = $(TOOL_PREFIX)-objcopy
OBJDUMP = $(TOOL_PREFIX)-objdump
CPP = $(CC) -E
#########################################################################
#################
# General flags #
#################
# (preprocessor flags)
# GCC include directory (of specific toolchain)
gccincdir := $(shell $(CC) -print-file-name=include)
# Debug and Disable optimisation
CPPFLAGS += -g -O0
# 32-bit Architecture
CPPFLAGS += -march=i386 -mpreferred-stack-boundary=2
# Warn on everything
CPPFLAGS += -Wall
# Include directories (do not use default system directories for header files)
CPPFLAGS += -nostdinc -I../u-boot/include -I../u-boot/arch/x86/include -isystem $(gccincdir)
# For calls to u-boot functions
CPPFLAGS += -D__KERNEL__ -DREALMODE_BASE=0x7c0 -DCONFIG_X86 -D__I386__
# Emit DWARF unwind info as compiler generated .eh_frame section instead of using GAS .cfi_* directives.
CPPFLAGS += -fno-dwarf2-cfi-asm
# A unit compiled with -fstack-usage will generate an extra file that specifies
# the maximum amount of stack used, on a per-function basis. The file has the
# same basename as the target object file with a .su extension. Each line of
# this file is made up of three fields:
# * The name of the function.
# * A number of bytes.
# * One or more qualifiers: static, dynamic, bounded. The second field
# corresponds to the size of the known part of the function frame. The
# qualifier static means that the function frame size is purely static. It
# usually means that all local variables have a static size. In this case, the
# second field is a reliable measure of the function stack utilization. The
# qualifier dynamic means that the function frame size is not static. It
# happens mainly when some local variables have a dynamic size. When this
# qualifier appears alone, the second field is not a reliable measure of the
# function stack analysis. When it is qualified with bounded, it means that
# the second field is a reliable maximum of the function stack utilization. A
# unit compiled with -Wstack-usage will issue a warning for each subprogram
# whose stack usage might be larger than the specified amount of bytes. The
# wording is in keeping with the qualifier documented above.
CPPFLAGS += -fstack-usage
# Don't append extra code for stack protection
CPPFLAGS += -fno-stack-protector
# Do not reorder top-level functions, variables, and asm statements
CPPFLAGS += -fno-toplevel-reorder
# https://interrupt.memfault.com/blog/best-and-worst-gcc-clang-compiler-flags#-ffunction-sections--fdata-sections----gc-sections
# Give each function its own section
CPPFLAGS += -ffunction-sections
# A freestanding environment is one in which the standard library may not exist,
# and program startup may not necessarily be at "main". The option -ffreestanding
# directs the compiler to not assume that standard functions have their usual definition.
CPPFLAGS += -ffreestanding
##########
# Others #
##########
# Remove warnings ...
# -Wno-format-security -Wno-format-nonliteral
# C++ options
# CXXFLAGS += -fvisibility=hidden -fno-strict-aliasing
####################
# C specific flags #
####################
# Warn if a function is declared or defined without specifying the argument types
# Don't use GCC built-in functions
# (C only)
CFLAGS += -Wstrict-prototypes -fno-builtin
############################
# Assembler specific flags #
############################
ASFLAGS += $(CPPFLAGS)
# For calls to u-boot functions
ASFLAGS += -D__ASSEMBLY__
#################
# Objcopy flags #
#################
# Fill gaps between sections with 0xff
OBJCFLAGS += --gap-fill=0xff
#########################################################################
TARGET = hello_world
CRT = crt0.o stubs.o
all: $(TARGET)
clean:
rm -f *.o *.a *.bin *.su
rm -f $(TARGET)
#########################################################################
$(TARGET): %: %.o $(CRT)
$(LD) -g $(EX_LDFLAGS) -T asm.lds -o $@ $^
$(OBJCOPY) -O binary $@ $@.bin 2>/dev/null
#########################################################################
|
Beta Was this translation helpful? Give feedback.
2 replies
-
|
It does an objcopy call after creating the binary - is there different output if you use the executable |
Beta Was this translation helpful? Give feedback.
Answer selected by
A2va
-
|
Thanks, that worked by setting But at least the debugging works. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It does an objcopy call after creating the binary - is there different output if you use the executable
"${workspaceFolder}/x86/hello_world",directly?