Crossworks Debugger doesn't reference asm code during debugging

Hello!

I'm using the complete crossworks toolchain, but I'm building my project with an own makefile using the shipped gcc toolchain by Crossworks. For debugging purposes I'm building my asm source code with some paths to the original asm source code. cc1 is adding the paths to the source files. It looks like this:

# 1 "c:/Users/andreas/Workspaces/AOAA/Demo/build/../src/thumb_crt0.s"
# 1 "C:\\Users\\andreas\\Workspaces\\AOAA\\Demo\\build//"
# 1 "<built-in>"
# 1 "<command-line>"
# 1 "c:/Users/andreas/Workspaces/AOAA/Demo/build/../src/thumb_crt0.s"
# 53 "c:/Users/andreas/Workspaces/AOAA/Demo/build/../src/thumb_crt0.s"
.global _start
.extern main
.global exit

.section .init, "ax"
.code 16
.align 2
.thumb_func

.....

If the code is built with cc1 like this, the Crossworks Debugger can find my source files (absolute file paths) and single stepping during debugging is possible. Normally I pass the relative path to cc1 not the absolute path. Then the asm source file including the debugging information looks like this:

# 1 "../src/thumb_crt0.s"
# 1 "C:\\Users\\andreas\\Workspaces\\AOAA\\Demo\\build//"
# 1 "<built-in>"
# 1 "<command-line>"
# 1 "../src/thumb_crt0.s"
# 53 "../src/thumb_crt0.s"
.global _start
.extern main
.global exit

.section .init, "ax"
.code 16
.align 2
.thumb_func

.....

Now the relative paths are included in the asm source file. But if I'm using relative paths the Crossworks Debugger can't find my source files and so I can't add a breakpoint in my asm code nor doing single stepping.

Is this a debugger restriction? Is there a way to add path "source file find path" in the Crossworks Debugger configuration? I prefer using relative paths.

Thanks and best regards,

Andreas