Rockbox Development > New Ports

Sansa Fuze+

<< < (13/162) > >>

kerobaros:
Okay, I have compiled a bootloader.elf, and am trying to pack it into the .sb file following the instructions on the wiki. However, elf2sb segfaults every time I run it.

From my dmesg:

--- Quote ---[ 3185.897354] elftosb[13167]: segfault at 30303044 ip 0804cb60 sp bf8db8b8 error 4 in elftosb[8048000+7000]
[ 3206.972947] elftosb[13229]: segfault at 30303044 ip 0804cb60 sp bfffbf48 error 4 in elftosb[8048000+7000]
[ 3227.578542] elftosb[13292]: segfault at 30303044 ip 0804cb60 sp bfe53768 error 4 in elftosb[8048000+7000]
[ 3279.296148] elftosb[13445]: segfault at 30303044 ip 0804cb60 sp bf90be38 error 4 in elftosb[8048000+7000]
--- End quote ---

Running Arch Linux x86, compiled the toolchain using the automatic method from the wiki. Help? :D

pamaury:
Strange,
normally elftosb is compiled in debug mode by default, can you use gdb or valgrind to see where it segfaults ?
If you don't know how to do this or just can't, could you send me both the bootloader.elf file and the elftosb binary ?

kerobaros:

--- Quote ---(gdb) run bootloader.db fuze+_key_file.txt bootloader.sb
Starting program: /home/kerobaros/fuze/elftosb bootloader.db fuze+_key_file.txt bootloader.sb

Program received signal SIGSEGV, Segmentation fault.
0x0804cb60 in elf_get_nr_sections (params=0x8050018) at elf.c:467
467           sec = sec->next;
--- End quote ---

Does that help at all? (Also: I didn't know how to use gdb, but apparently it's time to learn!)

pamaury:
That's really strange, I don't how it could segfault at this point.
The simplest solution is that you send me all the related files (the elf files which come from sbtoelf and bootloader.elf) since it will take you lots of time to debug it if you don't know how the program works.

kerobaros:
Alright. I sent you a message on IRC; could we discuss this there?

Navigation

[0] Message Index

[#] Next page

[*] Previous page