Rod,
I'm using Source Point 7.0.0. I can see the source files. I can display source, disassembly or mixed. However, the disassembly doesn't match up with the source code. There is a way to give Source Point an offset when the symbols are loaded, but I can't seem to get the right value. I know the address of _start and __protected_start but these labels are not in linuxbios_c.o. I need to find the location of a symbol in linuxbios_c.o to compute the offset.
Steve
-----Original Message----- From: Kittleson, Rodney C. Sent: Thursday, October 21, 2004 5:42 PM To: Kimball, Stephen; linuxbios@clustermatic.org Cc: Jeff_Pitts@arium.com Subject: RE: Makefile changes for symbols
Steve,
What version of Source point are you using? The symbols are coming in but SourcePoint doesn't allow me to reference the source files.
I mapped the linuxbios directory on my Win2000 system for SourcePoint to access. (I have samba running on my linux system) I just need to get SourcePoint working.
Thanks, Rod
-----Original Message----- From: Kimball, Stephen Sent: Wednesday, October 20, 2004 1:04 PM To: Kittleson, Rodney C.; linuxbios@clustermatic.org Cc: Jeff_Pitts@arium.com Subject: RE: Makefile changes for symbols
The file under your target in normal/linuxbios_c.o seems to have all the symbols if you add "-gdwarf-2" to the $CFLAGS in the Makefile. Then when you open the first C module the SourcePoint software asks where the file exists, after you tell SourcePoint it seems to find the rest by itself. I recreated the same Linux directory structure on Windows. Thanks Rod!
Steve
-----Original Message----- From: Kittleson, Rodney C. Sent: Wednesday, October 20, 2004 11:47 AM To: Kimball, Stephen; linuxbios@clustermatic.org Subject: RE: Makefile changes for symbols
Linuxbios_c, from the build directory, can be sucked into Sourcepoint to extract the symbols. This allows the disassembled instructions to display the symbols inline. It makes it easier to set breakpoints and follow the code, but it's a far cry from source level debugging.
I haven't attempted to link the source with sourcepoint yet. I may try it later this week, let me know if you have any success.
Rod
-----Original Message----- From: Kimball, Stephen Sent: Tuesday, October 19, 2004 3:33 PM To: linuxbios@clustermatic.org Subject: Makefile changes for symbols
Can someone give me the Makefile changes to make a LinuxBIOS with symbols? I tried adding "-gdwarf-2" to CFLAGS, but I'm not sure where the unstripped output would be.
Are there any features in the code that are useful in debugging LinuxBIOS? Any defines that should change as well?
Someone must have some experience with source code level debugging of LinuxBIOS with an American Arium ECM-50. Thanks.
Steve Kimball Benchmark Electronics Hudson, NH _______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios _______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios _______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
On Fri, 22 Oct 2004 Stephen.Kimball@bench.com wrote:
Rod,
I'm using Source Point 7.0.0. I can see the source files. I can display source, disassembly or mixed. However, the disassembly doesn't match up with the source code. There is a way to give Source Point an offset when the symbols are loaded, but I can't seem to get the right value. I know the address of _start and __protected_start but these labels are not in linuxbios_c.o. I need to find the location of a symbol in linuxbios_c.o to compute the offset.
there is a file we create called linuxbios.map, did you check that out?
ron
On Fri, 2004-10-22 at 11:33, Ronald G. Minnich wrote:
On Fri, 22 Oct 2004 Stephen.Kimball@bench.com wrote:
Rod,
I'm using Source Point 7.0.0. I can see the source files. I can display source, disassembly or mixed. However, the disassembly doesn't match up with the source code. There is a way to give Source Point an offset when the symbols are loaded, but I can't seem to get the right value. I know the address of _start and __protected_start but these labels are not in linuxbios_c.o. I need to find the location of a symbol in linuxbios_c.o to compute the offset.
there is a file we create called linuxbios.map, did you check that out?
ron
Since you brought it up. What's the Lxxxx stuff in the linuxbios.map file. There seems to be lots of labels starting with a "L" on the crt0.s code?
It looks like crt0.s runs first. The crt0.s code resets the process or 3 times. crt0.s calls hardwaremain ...
Steve
On Fri, 22 Oct 2004, Steve Kimball wrote:
Since you brought it up. What's the Lxxxx stuff in the linuxbios.map file. There seems to be lots of labels starting with a "L" on the crt0.s code?
Local symbols.
ron
Stephen.Kimball@bench.com writes:
Rod,
I'm using Source Point 7.0.0. I can see the source files. I can display source, disassembly or mixed. However, the disassembly doesn't match up with the source code. There is a way to give Source Point an offset when the symbols are loaded, but I can't seem to get the right value. I know the address of _start and __protected_start but these labels are not in linuxbios_c.o. I need to find the location of a symbol in linuxbios_c.o to compute the offset.
???
linuxbios_c is run at an absolute location in memory so the address of the symbols within it should be fine.
Look at readelf -a linuxbios_c.
Now these are not addresses within the rom chip. The are the addresses the code is copied to after memory initialization.
Currently romcc which generates the code that executes immediately out of the rom chip does not give good debugging output. But you should still be able to see the assembly. crt0.s should match what you are looking at.
You don't have the debugger in 16bit mode or something do you?
Eric