|
|
Atari demoscene BBS
| Re: Vlink internal error problem |
|---|
|
Posted by: Thadoss/Dune
|
Jan,06.2020-00:50
|
Hi George,
> 1. This is the definition of a bug - software should not throw internal error and die, something has gone really really bad!
I agree with you.
> 2. I'm puzzled by your quote that you can assemble the code under devpac. vasm can output tos binaries directly without linking. So why do you link in the first place?
I'll have a look at that.
Maybe vlink is not useful in my case after all (I only have asm code).
> 3. Looking at the error message it seems that the linker is confused by multiple data sections. Do you actually have multiple "data" or "section data" parts in your codebase?
Yes, a lot of them.
In fact, I'm coding in asm a bit like in object code :
1 file = 1 section text + 1 section data + 1 section bss.
Like this, I prefix all my variables, I do set / get prototypes and the code is easy to run and not spagghetti ;)
It compiles without problems and links well with devpack.
> Section 3 of the manual (http://sun.hasenbraten.de/vasm/release/vasm.html) shows the full syntax of the "section" directive:
.section <name>[,"<attributes>"][[,@<type>]|[,%<type>]|[,<mem_flags>]]
There are quire a few optional parameters you can use to define a section. Perhaps one of your "section" commands has some extra characters that might trigger something weird? (Or, more far fetched: does your source code has some garbage characters that aren't visible normally which vasm could pick up as parameter? DOS/Linux line endings spring to mind here, some text parsers can mistake a CR as illegal character)
My code is already quite big. But I'll try anyway to remove some code parts by parts... until I find the problem.
If I find it, I'll send a mail to Frank with pleasure.
> 5. This should have been (1) I guess: Have you tried using the latest vasm/vlink? It might be that this is a known bug that has been fixed.
Yes, I've tried both the latest one and an older one.
I'll tell you if I find something.
Thanks again
Laurent
|
[All messages in this thread] [Start new thread]
|
Topic
|
Posted by
|
Date
|
|
Vlink internal error problem
|
Thadoss/Dune
|
Jan,05.2020-19:21
|
|
Re: Vlink internal error problem
|
Emphii
|
Jan,05.2020-20:12
|
|
Re: Vlink internal error problem
|
Thadoss/Dune
|
Jan,05.2020-22:14
|
|
Re: Vlink internal error problem
|
ggn
|
Jan,06.2020-00:20
|
|
Re: Vlink internal error problem
|
Thadoss/Dune
|
Jan,06.2020-00:50
|
|
Re: Vlink internal error problem
|
evil
|
Jan,06.2020-19:22
|
|
Re: Vlink internal error problem
|
tat
|
Jul,26.2020-11:03
|
|
Re: Vlink internal error problem
|
Chain-Q
|
Jul,26.2020-14:57
|
|
Re: Vlink internal error problem
|
mikro
|
Jul,27.2020-07:56
|
|
Re: Vlink internal error problem
|
tat
|
Jul,27.2020-13:53
|
|
Re: Vlink internal error problem
|
mikro
|
Jul,28.2020-08:13
|
|
Re: Vlink internal error problem
|
mikro
|
Jul,29.2020-13:15
|
|
Re: Vlink internal error problem
|
tat
|
Jul,29.2020-16:22
|
What's the anti-troll code?
That's your personal code to be able to add comments and messages on the dhs.nu site.
Don't have a code or forgot it? Fix it here.
|
