添加函数调用如何导致链接时其他符号变得未定义?
我希望有人能够帮助解决我认为的链接器脚本问题。
添加对新函数的调用后,我遇到了一个奇怪的问题。如果没有函数调用,我的对象文件可以正确链接,但是,添加新函数调用后,我从另一个对象文件中获得对符号的未定义引用(我已经使用 objdump 验证了它实际上存在)。
同样奇怪的是,在存在函数调用的情况下,如果我首先使用 ld -r (提供可重定位输出)链接所有对象文件,然后使用我的链接脚本,则没有未定义的引用,但似乎链接脚本被忽略,因为输出二进制文件没有正确的入口点。
我的(交叉编译器)ld版本:
> i586-elf-ld --版本
GNU ld(GNU Binutils)2.20.1.20100303
我尝试证明“丢失”符号存在:
> i586-elf-ld -T link.ld -o kernel32.bin kernel_loader.o main.o stdio.o common.o gdt.o gdt.bin -y putch
main.o:对 putch 的引用 stdio.o: putch 的定义 main.o:在函数“main”中: main.c:(.text+0x1f): 对 `putch' 的未定义引用
NB(当我生成此输出时,我使用的文件名是gdt.bin 用于 nasm 编译的汇编程序,它只是另一个 .o 文件,真的)
我可以在相应的目标文件中看到“丢失”的符号:
> i586-elf-objdump -ht stdio.o
<前><代码>部分: Algn 中的 Idx 名称大小 VMA LMA 文件 0.文本000002f9 00000000 00000000 00000034 2**2 内容、分配、加载、RELOC、只读、代码 1 .数据 0000000c 00000000 00000000 00000330 2**2 内容、分配、加载、数据 2.bss 00000008 00000000 00000000 0000033c 2**2 分配 3.评论 00000012 00000000 00000000 0000033c 2**0 内容,只读 符号表: 00000000 l df *ABS* 00000000 stdio.c 00000000 ld .text 00000000 .text 00000000 ld .data 00000000 .data 00000000ld.bss 00000000.bss 00000000 ld .评论 00000000 .评论 00000000 g F .text 00000016 strlen 00000016 g F .text 0000005c 滚动 00000008 g O .data 00000004 numrows 00000004 g O .bss 00000004 ypos 00000004 g O .data 00000004 numcols 00000004 O *COM* 00000004 screen_mem 00000000 *UND* 00000000 memcpy 00000000 *UND* 00000000 memsetw 00000072 g F .text 0000007d 换行符 00000000克O.bss 00000004 xpos 000000ef g F .text 0000002e writech 00000000 g O.数据 00000004 颜色 0000011d g F .text 00000061 cls 0000017e g F.text 00000010 init_video 0000018e g F .text 00000133 putch 000002c1 g F .text 00000037 放置 000002f8 g F .text 00000001 set_text_color
stdio.o:文件格式 elf32-i386
以及具有未解析引用的目标文件:
> i586-elf-objdump -ht main.o
main.o:文件格式 elf32-i386 部分: Algn 中的 Idx 名称大小 VMA LMA 文件 0.文本0000007f 00000000 00000000 00000034 2**2 内容、分配、加载、RELOC、只读、代码 1 .数据 00000000 00000000 00000000 000000b4 2**2 内容、分配、加载、数据 2.bss 00000000 00000000 00000000 000000b4 2**2 分配 3 .rodata.str1.1 00000024 00000000 00000000 000000b4 2**0 内容、分配、加载、只读、数据 4.评论 00000012 00000000 00000000 000000d8 2**0 内容,只读 符号表: 00000000 l df *ABS* 00000000 main.c 00000000 ld .text 00000000 .text 00000000 ld .data 00000000 .data 00000000ld.bss 00000000.bss 00000000 ld .rodata.str1.1 00000000 .rodata.str1.1 00000000 ld .评论 00000000 .评论 00000000 g F .text 0000007f 主 00000000 *UND* 00000000 init_video 00000000 *UND* 00000000 gdt_install 00000000 *UND* 00000000 推车 00000000 *UND* 00000000 看跌期权 00000018 O *COM* 00000001 gdt 00000006 O *COM* 00000001 gdtp
我的链接脚本(不确定它是否相关):
OUTPUT_FORMAT("binary")
ENTRY(start)
phys = 0x00100000;
SECTIONS
{
.text phys : AT(phys) {
code = .;
*(.text)
*(.rodata*)
. = ALIGN(4096);
}
.data . : AT(data)
{
data = .;
*(.data)
. = ALIGN(4096);
}
.bss . : AT(bss)
{
bss = .;
*(.bss)
. = ALIGN(4096);
}
end = .;
}
如果我注释掉 main.c 中对 putch 的调用,我会得到对 put 的未定义引用...如果我删除对 gdt_install 的调用,没有错误!
gdt_install位于C文件中,但gdt_install调用了gdt.asm中定义的函数。
void gdt_install() {
/* ... */
gdt_reset();
}
[bits 32]
[section .text]
global gdt_reset
extern gdtp
gdt_reset:
lgdt [gdtp]
mov ax, 0x10 ; 0x10 offset for data segment (sizeof(struct gdt_entry) * 2)
mov ds, ax
mov es, ax
mov fs, ax
mov gs, ax
mov ss, ax
jmp 0x08:gdt_reset2 ; 0x08 offset for code segment (sizeof(struct gdt_entry))
gdt_reset2:
ret ; ret back to C
为了尝试进一步诊断原因,我一直在尝试重新创建错误。如果我将 gdt_install() 函数调用移动到源代码中的特定位置,我不会收到任何错误,并且一切正常:
int main() {
init_video();
putch('A');
puts("<- print a single char there...\n");
gdt_install();
puts("asdf\n\n");
int i;
for (i = 0; i < 15; ++i) {
if (i % 2 == 0) {
puts("even\n");
} else {
puts("odd\n");
}
}
return 0;
}
如果我将调用移到第一个 put() 调用上方,我会收到 put 的未定义引用! :
...
init_video();
putch('A');
gdt_install();
puts("<- print a single char there...\n");
puts("asdf\n\n");
...
i586-elf-ld -T link.ld -o kernel32.bin kernel_loader.o main.o stdio.o common.o gdt.o gdt_asm.o
main.o: In function `main':
main.c:(.text+0x2b): undefined reference to `puts'
main.c:(.text+0x37): undefined reference to `puts'
main.c:(.text+0x51): undefined reference to `puts'
main.c:(.text+0x63): undefined reference to `puts'
接下来,如果我将调用移至 putch() 之上,则会导致对 putch 的未定义引用(这是我最初进行调用的位置):
...
init_video();
gdt_install();
putch('A');
puts("<- print a single char there...\n");
puts("asdf\n\n");
...
main.o: In function `main':
main.c:(.text+0x1f): undefined reference to `putch'
最后,在 init_video() 之上,会导致对 init_video 未定义的引用:
...
gdt_install();
init_video();
putch('A');
puts("<- print a single char there...\n");
puts("asdf\n\n");
...
main.o: In function `main':
main.c:(.text+0x15): undefined reference to `init_video'
到底是什么导致这个错误?就像 gdt_install 调用以某种方式“破坏”其他符号一样......我在任何文档中都找不到对它的任何引用,但是 gdt_install 函数调用是否有某种方式可能导致某些链接器“边界”溢出,破坏其他代码?
有没有人遇到过这样的问题,或者有任何进一步调查的想法?我已在 osdev 论坛上发布:http://forum.osdev。 org/viewtopic.php?f=1&t=22227 但运气不太好。
谢谢
编辑:
我不确定它是否相关,但是如果我在链接时省略链接脚本,所有以前的错误都会消失......(尽管如此,我的引导加载程序无法调用内核,因为它不不理解 elf 二进制文件)。
根据要求,这是从编译后的 main.o 文件中预处理和反汇编前后的 main.c 文件。
预处理之前:
#include <stdio.h>
#include <common.h>
#include <gdt.h>
int main() {
init_video();
putch('A');
gdt_install();
puts("<- print a single char there...\n");
puts("asdf\n\n");
int i;
for (i = 0; i < 15; ++i) {
if (i % 2 == 0) {
puts("even\n");
} else {
puts("odd\n");
}
}
return 0;
}
预处理之后:
i586-elf-gcc -Wall -O -fstrength-reduce -fomit-frame-pointer -fno-inline -nostdinc -nostdlib -fsigned-char -nostartfiles -nodefaultlibs -fno-builtin -fno-stack-protector -I./include -E main.c
# 1 "main.c"
# 1 "<built-in>"
# 1 "<command-line>"
# 1 "main.c"
# 1 "./include/stdio.h" 1
# 1 "./include/common.h" 1
typedef unsigned short ushort;
typedef unsigned char uchar;
typedef unsigned int uint;
typedef unsigned long ulong;
typedef int size_t;
void *memcpy(void *dst, const void *src, size_t n);
void *memset(void *dst, const char val, size_t n);
void *memsetw(void *dst, const ushort val, size_t n);
void *memseti(void *dst, const int val, size_t n);
# 5 "./include/stdio.h" 2
void cls();
void writech(char c);
void putch(char c);
void puts(char *str);
void set_text_colour(uchar f, uchar b);
void init_video();
size_t strlen(char *str);
# 2 "main.c" 2
# 1 "./include/gdt.h" 1
struct gdt_entry {
ushort limit_low;
ushort base_low;
uchar base_middle;
uchar access;
uchar granularity;
uchar base_high;
} __attribute__((packed));
struct gdt_ptr {
ushort limit;
uint base;
} __attribute__((packed));
void gdt_set_gate(int n, ulong base, ulong limit, uchar access, uchar gran);
void gdt_install();
extern void gdt_reset();
# 4 "main.c" 2
int main() {
init_video();
putch('A');
gdt_install();
puts("<- print a single char there...\n");
puts("asdf\n\n");
int i;
for (i = 0; i < 15; ++i) {
if (i % 2 == 0) {
puts("even\n");
} else {
puts("odd\n");
}
}
return 0;
}
再次编辑:
感谢 nategoose 建议 -g3 提供更好的反汇编输出:
main.o: file format elf32-i386
SYMBOL TABLE:
00000000 l df *ABS* 00000000 main.c
00000000 l d .text 00000000 .text
00000000 l d .data 00000000 .data
00000000 l d .bss 00000000 .bss
00000000 l d .rodata.str1.4 00000000 .rodata.str1.4
00000000 l d .rodata.str1.1 00000000 .rodata.str1.1
00000000 l d .stab 00000000 .stab
00000000 l d .stabstr 00000000 .stabstr
00000000 l d .comment 00000000 .comment
00000000 g F .text 0000007f main
00000000 *UND* 00000000 init_video
00000000 *UND* 00000000 putch
00000000 *UND* 00000000 gdt_install
00000000 *UND* 00000000 puts
Disassembly of section .text:
00000000 <main>:
#include <stdio.h>
#include <common.h>
#include <gdt.h>
int main() {
0: 8d 4c 24 04 lea 0x4(%esp),%ecx
4: 83 e4 f0 and $0xfffffff0,%esp
7: ff 71 fc pushl -0x4(%ecx)
a: 55 push %ebp
b: 89 e5 mov %esp,%ebp
d: 53 push %ebx
e: 51 push %ecx
init_video();
f: e8 fc ff ff ff call 10 <main+0x10>
putch('A');
14: 83 ec 0c sub $0xc,%esp
17: 6a 41 push $0x41
19: e8 fc ff ff ff call 1a <main+0x1a>
gdt_install();
1e: e8 fc ff ff ff call 1f <main+0x1f>
puts("<- print a single char there...\n");
23: c7 04 24 00 00 00 00 movl $0x0,(%esp)
2a: e8 fc ff ff ff call 2b <main+0x2b>
puts("asdf\n\n");
2f: c7 04 24 00 00 00 00 movl $0x0,(%esp)
36: e8 fc ff ff ff call 37 <main+0x37>
3b: 83 c4 10 add $0x10,%esp
int i;
for (i = 0; i < 15; ++i) {
3e: bb 00 00 00 00 mov $0x0,%ebx
if (i % 2 == 0) {
43: f6 c3 01 test $0x1,%bl
46: 75 12 jne 5a <main+0x5a>
puts("even\n");
48: 83 ec 0c sub $0xc,%esp
4b: 68 07 00 00 00 push $0x7
50: e8 fc ff ff ff call 51 <main+0x51>
55: 83 c4 10 add $0x10,%esp
58: eb 10 jmp 6a <main+0x6a>
} else {
puts("odd\n");
5a: 83 ec 0c sub $0xc,%esp
5d: 68 0d 00 00 00 push $0xd
62: e8 fc ff ff ff call 63 <main+0x63>
67: 83 c4 10 add $0x10,%esp
puts("asdf\n\n");
int i;
for (i = 0; i < 15; ++i) {
6a: 43 inc %ebx
6b: 83 fb 0f cmp $0xf,%ebx
6e: 75 d3 jne 43 <main+0x43>
puts("odd\n");
}
}
return 0;
}
70: b8 00 00 00 00 mov $0x0,%eax
75: 8d 65 f8 lea -0x8(%ebp),%esp
78: 59 pop %ecx
79: 5b pop %ebx
7a: 5d pop %ebp
7b: 8d 61 fc lea -0x4(%ecx),%esp
7e: c3 ret
现在干净 make 的新输出:
$ make
nasm -f elf kernel_loader.asm -o kernel_loader.o
i586-elf-gcc -Wall -O0 -fstrength-reduce -fomit-frame-pointer -fno-inline -nostdinc -nostdlib -fsigned-char -nostartfiles -nodefaultlibs -fno-builtin -fno-stack-protector -I./include -g3 -c main.c
i586-elf-gcc -Wall -O0 -fstrength-reduce -fomit-frame-pointer -fno-inline -nostdinc -nostdlib -fsigned-char -nostartfiles -nodefaultlibs -fno-builtin -fno-stack-protector -I./include -g3 -c stdio.c
i586-elf-gcc -Wall -O0 -fstrength-reduce -fomit-frame-pointer -fno-inline -nostdinc -nostdlib -fsigned-char -nostartfiles -nodefaultlibs -fno-builtin -fno-stack-protector -I./include -g3 -c common.c
i586-elf-gcc -Wall -O0 -fstrength-reduce -fomit-frame-pointer -fno-inline -nostdinc -nostdlib -fsigned-char -nostartfiles -nodefaultlibs -fno-builtin -fno-stack-protector -I./include -g3 -c gdt.c
nasm -f elf gdt.asm -o gdt_asm.o
i586-elf-ld -T link.ld -o kernel32.bin -\( kernel_loader.o main.o stdio.o common.o gdt.o gdt_asm.o -\)
main.o: In function `main':
/cygdrive/c/programming/os/kernel/main.c:12: undefined reference to `puts'
/cygdrive/c/programming/os/kernel/main.c:14: undefined reference to `puts'
/cygdrive/c/programming/os/kernel/main.c:20: undefined reference to `puts'
/cygdrive/c/programming/os/kernel/main.c:22: undefined reference to `puts'
make: *** [kernel32.bin] Error 1
编辑 3< /b>
根据要求,这是 nm -s 在 stdio.o 上的输出
i586-elf-nm -s stdio.o
00000042 T cls
00000000 D colour
00000000 T init_video
U memcpy
U memsetw
0000015e T newline
00000004 D numcols
00000008 D numrows
000001e4 T putch
0000024e T puts
00000004 C screen_mem
000000b8 T scroll
00000291 T set_text_colour
00000016 T strlen
00000199 T writech
00000000 B xpos
00000004 B ypos
编辑 4 根据要求,这里是整个源文件。我已将 zip 文件上传到:http://www.owenstephens。 co.uk/media/files/kernel.zip 感谢您持续的关注和帮助,非常感谢!
Makefile:
NASM=nasm
GCC=i586-elf-gcc
LD=i586-elf-ld
FMT=-f elf
GFLAGS=-Wall -O0 -fstrength-reduce -fno-inline -nostdinc -nostdlib -fsigned-char -nostartfiles -nodefaultlibs -fno-builtin -fno-stack-protector -I./include -g3 -c
LFLAGS=-T link.ld
ALL=kernel_loader.o main.o stdio.o common.o gdt.o gdt_asm.o
INCLUDES=include/stdio.h include/common.h include/gdt.h
all: $(ALL) kernel32.bin
kernel_loader.o: kernel_loader.asm
$(NASM) $(FMT) $*.asm -o $@
main.o: main.c
$(GCC) $(GFLAGS) $<
stdio.o: stdio.c include/stdio.h
$(GCC) $(GFLAGS) $<
common.o: common.c include/common.h
$(GCC) $(GFLAGS) $<
gdt.o: gdt.c include/gdt.h
$(GCC) $(GFLAGS) $<
gdt_asm.o: gdt.asm
$(NASM) $(FMT) $< -o $@
kernel32.bin: $(ALL) $(INCLUDES)
$(LD) $(LFLAGS) -o $@ -\( $(ALL) -\)
clean:
rm -f $(ALL) kernel32.bin
链接脚本:
OUTPUT_FORMAT("binary")
ENTRY(_start)
phys = 0x00100000;
SECTIONS
{
.text phys : AT(phys) {
code = .;
*(.text)
*(.rodata*)
. = ALIGN(4096);
}
.data . : AT(data)
{
data = .;
*(.data)
. = ALIGN(4096);
}
.bss . : AT(bss)
{
bss = .;
*(.bss)
. = ALIGN(4096);
}
end = .;
}
main.c:
#include <stdio.h>
#include <common.h>
#include <gdt.h>
int main() {
gdt_install();
puts("This is a minimal example...");
return 0;
}
common.c:
#include <common.h>
void *memcpy(void *dst, const void *src, size_t n) { return (void *)0; }
void *memset(void *dst, const char val, size_t n) { return (void *)0; }
void *memsetw(void *dst, const ushort val, size_t n) { return (void *)0; }
void *memseti(void *dst, const int val, size_t n) { return (void *)0; }
stdio.c:
#include <stdio.h>
#include <common.h>
ushort *screen_mem;
int colour = 0x0F;
int xpos = 0, ypos = 0;
int numcols = 80, numrows = 25;
void init_video() {}
size_t strlen(char *str) { return 0; }
void cls() { }
inline void scroll() { }
inline void newline() { }
void writech(char c) { }
void putch(char c) { }
void puts(char *str) { }
void set_text_colour(unsigned char f, unsigned char b){ }
gdt.c:
#include <gdt.h>
struct gdt_entry gdt[3];
struct gdt_ptr gdtp;
void gdt_set_gate(int n, ulong base, ulong limit, uchar access, uchar gran) { }
void gdt_install() { }
gdt.asm:
global gdt_reset
gdt_reset:
ret
gdt_reset2:
ret
include/common.h:
#ifndef __COMMON_H
#define __COMMON_H
typedef unsigned short ushort;
typedef unsigned char uchar;
typedef unsigned int uint;
typedef unsigned long ulong;
typedef int size_t;
void *memcpy(void *dst, const void *src, size_t n);
void *memset(void *dst, const char val, size_t n);
void *memsetw(void *dst, const ushort val, size_t n);
void *memseti(void *dst, const int val, size_t n);
#endif
include/stdio.h:
#ifndef __STDIO_H
#define __STDIO_H
#include <common.h>
void cls();
void writech(char c);
void putch(char c);
void puts(char *str);
void set_text_colour(uchar f, uchar b);
void init_video();
size_t strlen(char *str);
#endif
include/gdt.h:
#ifndef __GDT_H
#define __GDT_H
#include <common.h>
struct gdt_entry {
ushort limit_low;
ushort base_low;
uchar base_middle;
uchar access;
uchar granularity;
uchar base_high;
} __attribute__((packed));
struct gdt_ptr {
ushort limit;
uint base;
} __attribute__((packed));
void gdt_set_gate(int n, ulong base, ulong limit, uchar access, uchar gran);
void gdt_install();
extern void gdt_reset();
#endif
“objdump -t”共享库的输出,其中包含所有 .o 文件(kernel_loader 除外,因此未定义的 _start 符号。
> i586-elf-objdump -t libos.so.1.0.1
libos.so.1.0.1: file format elf32-i386
SYMBOL TABLE:
08048080 l d .text 00000000 .text
08048162 l d .rodata 00000000 .rodata
08049180 l d .data 00000000 .data
0804918c l d .bss 00000000 .bss
00000000 l d .stab 00000000 .stab
00000000 l d .stabstr 00000000 .stabstr
00000000 l d .comment 00000000 .comment
00000000 l df *ABS* 00000000 main.c
00000000 l df *ABS* 00000000 stdio.c
00000000 l df *ABS* 00000000 common.c
00000000 l df *ABS* 00000000 gdt.c
00000000 l df *ABS* 00000000 gdt.asm
08048161 l .text 00000000 gdt_reset2
08049180 g O .data 00000004 colour
08048125 g F .text 00000014 memsetw
0804918c g O .bss 00000004 xpos
08049188 g O .data 00000004 numrows
08048158 g F .text 00000005 gdt_install
08048108 g F .text 0000000a memcpy
080480ee g F .text 00000005 puts
08049198 g O .bss 00000018 gdt
08049194 g O .bss 00000004 screen_mem
080480e0 g F .text 0000000e putch
08048144 g F .text 00000014 gdt_set_gate
00000000 *UND* 00000000 _start
08048160 g .text 00000000 gdt_reset
080480b4 g F .text 00000005 init_video
080480c8 g F .text 00000005 scroll
0804918c g *ABS* 00000000 __bss_start
08048112 g F .text 00000013 memset
08048080 g F .text 00000033 main
080480f3 g F .text 00000014 set_text_colour
080480cd g F .text 00000005 newline
08049190 g O .bss 00000004 ypos
080491b0 g O .bss 00000006 gdtp
0804918c g *ABS* 00000000 _edata
080491b8 g *ABS* 00000000 _end
080480c3 g F .text 00000005 cls
080480b9 g F .text 0000000a strlen
08048139 g F .text 0000000a memseti
08049184 g O .data 00000004 numcols
080480d2 g F .text 0000000e writech
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(7)
这听起来像是链接线上的循环引用问题。链接器按顺序遍历目标文件并“记住”任何未解析的外部文件。但是,它也可以丢弃任何没有引用它们的对象文件。如果两个或多个目标文件相互引用(导致循环引用),则链接器可能无法跟踪未解析的实体。
尝试复制链接线的部分,然后将其缩小到您需要的范围。
This sounds like a circular reference problem on the link line. The linker goes through the object files in order and "remembers" any unresolved externals. However, it also can discard any object files that don't have references to them. If two or more object files reference each other (causing a circular reference), the linker may not be able to track the unresolved entities.
Try duplicating portions of the link line, and then narrow it down to what you need.
命令行上的文件顺序似乎与 GNU 链接器有关。首先将包含入口点 (
kernel_loader.o
) 的.o
文件放在命令行上,然后是它直接引用的任何对象,然后是这些对象引用的对象 (并且尚未在命令行上)等,或者链接器可能会丢失一些文件。The order of files on the command line seems to matter with the GNU linker. Put the
.o
file containing the entry point (kernel_loader.o
) first on the command line, then any objects that it directly references, then the objects referenced by those objects (and that aren't already on the cmd-line), etc., or it's possible that the linker will miss some files.还有另一个SO问题(可能相似/相同,我不确定)涵盖其中一些。那一个提供任何帮助吗?
There is another SO question (may be similar/identical, I'm not sure) which covers some of this. Does that one offer any help?
我已经见过几次类似的问题,在某个时刻,就在我彻底发疯之前,我开始寻找可能最终出现在名称中的看不见的东西。非 ASCII 字节或不可打印的 ASCII 字符可能会潜入源代码并将其附加到
gdt_install();
之后看到的第一个代码中,您可能需要尝试添加注释或空宏 (或在调用
gdt_install()
和下一个实际代码行之间的do{}while(0)
)。甚至可以将光标放在函数名称中,并将其返回到该函数名称的第一个字符之前,然后开始输入您决定在其中添加的任何内容。如果它是由 gdt_install(); 的存在引起的,那么在那里抛出的其他东西应该会导致不同的错误。如果您还没有准备好,您可能想通过调用
gdt_install()
查看文件的预处理器输出及其汇编输出。如果这些都没有产生任何有趣的结果,请更改 gdt_install 的名称,看看是否会发生任何变化。我见过一些编译器和/或链接器中的错误可能会产生类似这样奇怪的结果的实例。也许用作符号表的哈希表中存在错误(甚至可能在 elf 文件的哈希表中)。
希望你能弄清楚这一点。
I've seen similar problems a few times and at a certain point, just before I go stark raving mad, I start to look for invisible things that might end up in the names. Non-ASCII bytes or non-printable ASCII characters that could have snuck into your source code and attached themselves to the first code seen after
gdt_install();
You might want to try adding a comment or empty macro (or a
do{}while(0)
) between your call togdt_install()
and the next real line of code. Maybe even go as far as placing your cursor in the function name and back it up to just before the first character of that function name and start typing whatever you decide to add there. If it is something caused by the presence ofgdt_install();
then something else getting thrown in there should force a different error.If you haven't already, you may want to view the preprocessor output of the file with the call to
gdt_install()
as well as its assembly output.If none of that produces anything interesting, change the name of
gdt_install
and see if that changes anything. I've seen a few instances where bugs in the compiler and/or linker could produce something odd like this. Perhaps a bug in a hash table used as a symbol table (maybe even in the elf file's hash table).Hope you figure this out.
一些疯狂的猜测,也许您在 gdt_install 中调用(并且可能是内联)的汇编器函数弄乱了后面的内容。 (在
ret
之前的最后跳转很不寻常,从未见过)您的
gdt_install
是否与您进行调用的编译单元位于同一编译单元中?你使用-O[12]
进行编译吗?调用是否内联?编译器为调用方生成的汇编程序是什么样的?您是否尝试使用
-O0 -g
或-fno-inline
进行编译(或者如何调用此选项)?some wild guess, perhaps your assembler function which is called (and probably inlined) in
gdt_install
is messing up what is coming after it. (this jump at the end before theret
is unusual, never seen that)Is your
gdt_install
in the same compilation unit as where you have the call? Do you use-O[12]
for compilation? Is the call inlined? How does the assembler that the compiler produces for the call side look like?Did you try to compile with
-O0 -g
or-fno-inline
(or how this option is called)?你写的。 “
我已经实现了自己的 psuedo-stdio 函数(puts、puch...),这些函数完全匹配...
”您是否使用了标准 libc 中的任何内容?如果不是,您应该将-nostdlib
添加到命令行中。当我尝试覆盖标准 libc 中的函数时,我发现奇怪的事情发生了。You wrote. "
I've implemented my own psuedo-stdio functions (puts, putch...) the functions match exactly ...
" Are you using anything in the standard libc? If you aren't, you should add-nostdlib
to your command line. I have seen strange things happen when I've tried to override functions in the standard libc.我怀疑 nasm 生成的对象和 gcc/gas 生成的对象的链接符号表的组合可能会弄乱一些东西。
您能否尝试将对
gtd_install
的调用替换为对包含内联程序集的短内联函数的调用,该函数调用或跳转到gtd_install
并驻留在与当前调用相同的文件中gtd_install
?我突然想到的另一件事是,如果 gtd_install 是用汇编语言编写的,那么它在语法上可能不是 100% 正确。我从来没有见过这样的东西,但只是认为 gtd_install 的边界(特别是结尾)或其大小可能没有由汇编器正确确定,而这只是随机结果。
除此之外,我认为您必须去找 binutils 人员并直接向他们寻求帮助。
I suspect that perhaps the combining of the linking symbol tables from the nasm generated object and the gcc/gas generated objects might be messing something up.
Could you try replacing the call to
gtd_install
with a call to a short inline function containing inline assembly that calls or jumps togtd_install
and resides in the same file as the current call togtd_install
?Another thing that just popped into my mind is that if
gtd_install
is written in assembly language then it is possible that it might not be 100% syntactically correct. I've never seen anything like this, but just thinking that it might be possible thatgtd_install
's boundaries (particularly the end) or its size is not correctly determined by the assembler, and that is just having random-ish results.Baring that I think you're going to have to go to the binutils folks and ask them for help directly.