[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tcf-dev] Overview needed
|
Hi Stefan,
> The breakpoints are still not found...
It looks like your version of dbghelp.dll does not preserve file name case. I suggest to try latest dbghelp.dll. V6 dll is known to be broken.
> As I step through the code and call e.g. printf() Eclipse does not step over the function...
Step over can fail if stack tracing fails, and good stack tracing needs symbols for system dlls, which could be downloaded from Microsoft symbol servers, but this functionality is not implemented in the TCF agent.
Note that Windows debugging support in TCF is more like a demo, folks here are mostly interested in embedded systems, which use ELF/DWARF binary file formats, like, for example, Linux.
Regards,
Eugene
-----Original Message-----
From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of Stefan.Falk@xxxxxxxxxxxx
Sent: Donnerstag, 12. Dezember 2013 00:28
To: tcf-dev@xxxxxxxxxxx
Subject: Re: [tcf-dev] Overview needed
Hi!
Thank you for your answers Christophe and Martin and sorry that my answer comes with such long delay!
I build my little test-program now with the Microsoft Visual C++ toolchain which works so far. Now I am able to debug C code but there are still some issues: The breakpoints are still not found and the program stops somewhere inside the ntdll.dll before the code jumps to my actual main file. As I step through the code and call e.g. printf() Eclipse does not step over the function but instead starts to debug inside MSVCR100.dll - which is not really what I want. :D
I send you a screenshot and the TCF log in case you want to take a look at it.
The version of my dbghelp.dll file is v6.1 which should be okay I think.
As I debug the agent I see that the line gets resolved correctly. ModuleName is NULL but the function is called by setting this parameter NULL. I don't understand what causes this error.
Best regards,
Stefan
-----Original Message-----
From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of Oberhuber, Martin
Sent: Friday, December 06, 2013 4:21 PM
To: TCF Development
Subject: Re: [tcf-dev] Overview needed
Hello Stefan,
I assume that what you're trying to do is compile a local (native) debug agent with TCF, and then start replacing services until that debugger talks to your remote server/controller instead of the local host. This sounds like a reasonable approach ("top-down approach").
Have you seen the "TCF Agent Porting Guide", it should help you get more understanding on this task:
http://git.eclipse.org/c/tcf/org.eclipse.tcf.git/plain/docs/TCF%20Agent%20Porting%20Guide.html
Note that for debugging the PE format on Windows, you need an updated DBGHELP.DLL installed as per the porting guide.
Also note that in case you want to debug your agent, you might want to build it with Visual Studio (unless you like gdb).
http://git.eclipse.org/c/tcf/org.eclipse.tcf.git/plain/docs/TCF%20Getting%20Started.html
I'll separately answer your other question regarding the daytime example.
I still think this "bottom-up approach" is also valuable for you.
So you approach your goals from 2 ends.
Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Architect - Development Tools, Wind River direct +43.662.457915.85 fax +43.662.457915.6
-----Original Message-----
From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of Christophe Augier
Sent: Friday, December 06, 2013 3:56 PM
To: tcf-dev@xxxxxxxxxxx
Subject: Re: [tcf-dev] Overview needed
Hi Stefan,
you won't be able to debug this file using the current implementation of TCF because the file you generated using MinGW is in the PE file format but the debug information are in DWARF. As far as I know this is not supported by TCF right now, only by GDB.
Do you confirm Eugene?
I suggest you build a new .exe file using Visual Studio which will generate a PE file with MS debug format or that you switch to a Linux host (ELF + DWARF).
Cheers,
- Christophe
On 12/6/2013 1:37 PM, Stefan.Falk@xxxxxxxxxxxx wrote:
> I think I am lost a little bit here. As I wasn't able to get the daytime from the daytime example I tried to debug a simple C program using the TCF. Debugging works so far, but the TCF agent does not seem to contain any symbol information. I compile the test program with MinGW.
>
> You might want to take a look at my SO question:
> http://stackoverflow.com/questions/20422492/tcf-debug-unresolved-sourc
> e-line-information
>
> My compiled object file is pe-i386 typed so I don't think this could be the problem here but what does the agent miss here?
>
>
> But besides that.. what I am trying to do is create an agent that communicates between Eclipse and a server. The server will offer functionality for a µController device such as runUntil(breakpoint) etc. and the agent will "only" have to receive this information, look up the correct line number which is mapped to the address where the device stopped and pass this information to eclipse such that this debug-stop can be visualized.
>
> At the moment I am sure that I will have to implement that mapping part on my own since the agent does not support the debug information being generated by SDCC. This and the actual part where the agent and my server exchange their data would have to be modified/written. The rest could stay as it is if I understood the agents purpose correctly.
>
>
> Would anyone be so kind helping me on my first issue und maybe give me a push into the right direction?
>
> _______________________________________________
> tcf-dev mailing list
> tcf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/tcf-dev
>
_______________________________________________
tcf-dev mailing list
tcf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tcf-dev
_______________________________________________
tcf-dev mailing list
tcf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tcf-dev
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
