DevPac and BSS DEBUG hunks

phx · 27 August 2024, 19:19

Years ago I realised that Devpac does neither create HCLN DEBUG hunks with "Line Debug = Compressed" nor LINE DEBUG hunks with "Line Debug = Standard" following a BSS section.

Therefore I did the same in vasm's hunk output module. But I see no real reason for it . Why don't you need a connection between hunk-offsets and source text lines in the BSS section? Am I missing something?

hop · Yesterday, 13:20

Surely source level debuggers would require this information to associate labels in BSS sections with source code line numbers.

Bruce Abbott · Today, 06:44

Quote:

Originally Posted by phx

Years ago I realised that Devpac does neither create HCLN DEBUG hunks with "Line Debug = Compressed" nor LINE DEBUG hunks with "Line Debug = Standard" following a BSS section.

Therefore I did the same in vasm's hunk output module. But I see no real reason for it . Why don't you need a connection between hunk-offsets and source text lines in the BSS section? Am I missing something?

The purpose of line debug is for showing the source line when stepping through code in a debugger. No code in BBS so...

phx · Today, 13:58

Quote:

Originally Posted by Bruce Abbott

The purpose of line debug is for showing the source line when stepping through code in a debugger. No code in BBS so...

Could be an explanation. But why are there LINE DEBUG hunks for the DATA sections then? Maybe because nobody can stop you from putting code into a data section?

Anyway, I decided now that vasm will output LINE DEBUG hunks for BSS, unless strict Devpac-compatibility was selected (

-devpac

option). Some debuggers may need it nevertheless.

kamelito · Today, 17:32

@PHX does Vasm throw a warning if code is put in data sections? (Or datas in code)

27 August 2024, 19:19	#1
phx Natteravn Join Date: Nov 2009 Location: Herford / Germany Posts: 2,584	DevPac and BSS DEBUG hunks Years ago I realised that Devpac does neither create HCLN DEBUG hunks with "Line Debug = Compressed" nor LINE DEBUG hunks with "Line Debug = Standard" following a BSS section. Therefore I did the same in vasm's hunk output module. But I see no real reason for it . Why don't you need a connection between hunk-offsets and source text lines in the BSS section? Am I missing something?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Devpac & Devpac 2 manuals?	RetrogamerRhys	Coders. Asm / Hardware	4	07 July 2024 20:28
Devpac Debug hunks	phx	Coders. General	21	16 July 2023 08:13
Devpac Debug Issue with multiple files	sandruzzo	Coders. General	49	05 October 2021 17:13
Devpac II or Devpac 3 assembler with manual.	RetrogamerRhys	MarketPlace	2	01 February 2020 18:33
Devpac - CNOP in a BSS Section	h0ffman	Coders. Asm / Hardware	30	18 March 2015 23:12

Yesterday, 13:20	#2
hop Registered User Join Date: Apr 2019 Location: UK Posts: 279	Surely source level debuggers would require this information to associate labels in BSS sections with source code line numbers.

Today, 17:32	#5
kamelito Zone Friend Join Date: May 2006 Location: France Posts: 1,897	@PHX does Vasm throw a warning if code is put in data sections? (Or datas in code)

Currently Active Users Viewing This Thread: 2 (1 members and 1 guests)
a/b