[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-debug-dev] GDB command file path problem

Hi Sergey, I think this question would be better asked on the CDT mailing list: cdt-dev@xxxxxxxxxxx

Michael Rennie

Inactive hide details for Сергей Смирнов ---04/26/2011 06:32:58 AM---Hello, I seem to find a problem in Eclipse DeСергей Смирнов ---04/26/2011 06:32:58 AM---Hello, I seem to find a problem in Eclipse Debug. I'm using Eclipse Helios (3.6) with AVR Eclipse Pl

From: Сергей Смирнов <55555sergey55555@xxxxxxx>
To: platform-debug-dev@xxxxxxxxxxx
Cc: Олег Большаков <viona31@xxxxxxxxx>
Date: 04/26/2011 06:32 AM
Subject: [platform-debug-dev] GDB command file path problem
Sent by: platform-debug-dev-bounces@xxxxxxxxxxx

Hello, I seem to find a problem in Eclipse Debug.

I'm using Eclipse Helios (3.6) with AVR Eclipse Plugin for debugging C-programs with avr-gdb and simulavr as AVR MCU simulator.
The bug is connected with gdb preferences which are set in debug configuration preferences page.
I'm using specially compiled gdb for AVR architecture (avr-gdb.exe) but the problem seems to be general for all gdb debuggers.
The problem is connected with "GDB command file" option on the Debugger tab of Debugger Confugurations Window.
When I leave this option empty (not inputing the file path with gdb commands) I have my avr-gdb + simulavr system work fine (although I evidently have to execute all the necessary init commands by myself manually in Eclipse Console View for avr-gdb). When I try to specify the GDB commands file path Eclipse seems to behave uncorrectly. Eclipse behaves uncorrectly if I specify a path to any file:
1) to a correct file with just one command "load" (when executing load in Eclipse console view everything works fine)
2) to an empty file or
3) to an unexisting path (wrong file path).
I also can find some strange errors in Eclipse Console log.
You can find two logs attached to the message: ok_log.txt and fail_log.txt.
Consider the beginning of the fail log: it begins with

"warning: Can not parse XML target description; XML support was disabled at compile time
hfhhg: No such file or directory"

("hfhhg" was our file path name to an unexsisting file).

This message appears after gdb is connected to simulavr via tcp connection and gets from simulavr some XML which can not be parsed.
This error is not the source of my problem because I can see the same message in ok_log and it works fine actually.

What is the question?

The point is that the above warning can be got after gdb connected to simulavr. To connect gdb to simulavr there should be a command "target remote localhost:1212" (I set the necessary parameters in the Debug configuration tab).
So why does the behaviour of Eclipse differs when the GDB command file path is set and when it's not?
Why when the path is not set the first command to be sent is

<number>-gdb-set confirm off

and when the path is set I can see the first command to be set is a connection command (and the above warning as the result)?

Does Eclipse launches gdb with smth like "--eval-command" parameter to perform connection command?
(I suggest Eclipse don't loose any console commands and that is really the first one when file path is specified).

If you need I'll specify all the rest settings and actions.

Sergey Smirnov[attachment "ok_log.txt" deleted by Michael Rennie/Ottawa/IBM] [attachment "fail_log.txt" deleted by Michael Rennie/Ottawa/IBM] _______________________________________________
platform-debug-dev mailing list

GIF image