On 04/10/2014 07:33 PM, Martin Frb wrote:
Look at the log, if you see the -exec-... and the work then all is ok.
I have the ARM machine in question (a topless QNAP NAS) at home and
will try to make sense of this during the weekend.
BTW.:
In fact the helpful person from Austria did start to
On 04/10/2014 05:30 PM, Martin Frb wrote:
So I will not add those gdb/gdbserver myself.
I do not know, if anyone else wants to work on that.
I did try (see the other mail).
Also which installer should they be added to?
I suppose you mean installer for Lazarus ?
The only installer which does
On 11/04/2014 08:08, Michael Schnell wrote:
On 04/10/2014 05:30 PM, Martin Frb wrote:
So I will not add those gdb/gdbserver myself.
I do not know, if anyone else wants to work on that.
I did try (see the other mail).
Also which installer should they be added to?
I suppose you mean
Martin Frb wrote:
There are several possibilities, that I can think off:
1) some setting the IDE uses.
- Gather all the set foo= commands that the IDE sends, and see if
applying them to your manual driven gdb session makes a different.
- Run your manual gdb with gdb.exe -i mi to enable mi
On 11/04/2014 15:08, Bernd Mueller wrote:
Martin Frb wrote:
There are several possibilities, that I can think off:
1) some setting the IDE uses.
- Gather all the set foo= commands that the IDE sends, and see if
applying them to your manual driven gdb session makes a different.
- Run your
Martin Frb wrote:
I have the log file attached.
What code is on this line?
This is not always the same line when the problem appears.
repeat
Writeln('Test');
Sleep(500);
until FALSE;
It can happen, that I press F8, when the grey bar is on the line with
the Writeln
On 10/04/2014 12:28, Bernd Mueller wrote:
You could try, if you are on that line, instead of stepping (F8), set
a breakpoint the next line (lines, if there is a conditional), and
use F9.
Then, with F9 you should be able to use the pause button
And then try, what happens if you hit the
On 04/09/2014 06:27 PM, Bernd Mueller wrote:
I stepped through the program until the problem occurred and hit then
pause. As far as I could see, nothing happened. Then I hit stop.
I once was told that with using gdbserver, Pause (while not hitting a
breakpoint) is not possible.
That is
On 10/04/2014 14:14, Michael Schnell wrote:
On 04/09/2014 06:27 PM, Bernd Mueller wrote:
I stepped through the program until the problem occurred and hit then
pause. As far as I could see, nothing happened. Then I hit stop.
I once was told that with using gdbserver, Pause (while not hitting
Martin Frb wrote:
If gdb server can detect the connection loss (at stop), then it was
still connected. So gdb has failed on a different level. I assume that
the gdbserver on the arm target is the same, when you try from win7, as
it is when you try from win2000?
yes, I have only one target.
On 10/04/2014 15:06, Bernd Mueller wrote:
Martin Frb wrote:
gdbserver seems to have some options to track problems, maybe try them?
Options:
--debug Enable general debugging output.
This is very strange. If I activate --debug, then everything seems to
work. As if slowing down
On 04/10/2014 03:30 PM, Martin Frb wrote:
The IDE ssh debugger, can not pause the app either.
I don't understand why this should be the case.
Manually using gdb via ssh (to bash) can do it, So why should the IDE
not be able to ? (Or does - when in non-remote mode - the IDE really
send a
On 10/04/2014 16:06, Michael Schnell wrote:
On 04/10/2014 03:30 PM, Martin Frb wrote:
The IDE ssh debugger, can not pause the app either.
I don't understand why this should be the case.
Manually using gdb via ssh (to bash) can do it, So why should the IDE
not be able to ? (Or does - when
On 04/10/2014 05:06 PM, Michael Schnell wrote:
Manually using gdb via ssh (to bash) can do it, So why should the IDE
not be able to ? (Or does - when in non-remote mode - the IDE really
send a SigInt *directly* to the application and not via the debugger )
Hum.
Re-Thinking:
When manually
On 04/10/2014 03:30 PM, Martin Frb wrote:
On 10/04/2014 14:14, Michael Schnell wrote:
Moreover I found that, with an embedded target, finding or creating a
normal gdb might be a lot easier that finding or creating the cross
gdb (running on PC but understanding the Target's files) plus the
On 10/04/2014 16:16, Michael Schnell wrote:
On 04/10/2014 05:06 PM, Michael Schnell wrote:
Manually using gdb via ssh (to bash) can do it, So why should the IDE
not be able to ? (Or does - when in non-remote mode - the IDE really
send a SigInt *directly* to the application and not via the
On 04/10/2014 05:14 PM, Martin Frb wrote:
Or do you have another way?
A wild Idea might be to open two SSH sessions: one for gdb (maybe in
sync mode of this makes sense), and another that just accesses a little
SIGINTServer application that is used to send the signal when appropriate..
On 10/04/2014 16:20, Michael Schnell wrote:
On 04/10/2014 03:30 PM, Martin Frb wrote:
On 10/04/2014 14:14, Michael Schnell wrote:
Moreover I found that, with an embedded target, finding or creating
a normal gdb might be a lot easier that finding or creating the
cross gdb (running on PC but
On 10/04/2014 16:28, Michael Schnell wrote:
On 04/10/2014 05:14 PM, Martin Frb wrote:
Or do you have another way?
A wild Idea might be to open two SSH sessions: one for gdb (maybe in
sync mode of this makes sense), and another that just accesses a
little SIGINTServer application that is
On 04/10/2014 05:33 PM, Martin Frb wrote:
That would work. (and I would accept a patch (adding an option / not
making it mandatory)
Sounds nice to me, especially regarding that gdbserver is not that
common and hence not easily to come by in some cases.
But at this stage, I prefer the
Martin Frb wrote:
On 10/04/2014 15:06, Bernd Mueller wrote:
Martin Frb wrote:
gdbserver seems to have some options to track problems, maybe try them?
Options:
--debug Enable general debugging output.
This is very strange. If I activate --debug, then everything seems to
work.
On 10/04/2014 18:04, Bernd Mueller wrote:
If I use the standalone gdb on the Win7 Host instead of Lazarus,
debugging on the remote target works correct.
I had a look into the network traffic between target and host while
debugging with Lazarus. If the stepping fails, one can see that the
On 10/04/2014 16:41, Michael Schnell wrote:
On 04/10/2014 05:33 PM, Martin Frb wrote:
That would work. (and I would accept a patch (adding an option / not
making it mandatory)
Sounds nice to me, especially regarding that gdbserver is not that
common and hence not easily to come by in some
Hello,
I am using Lazarus 1.2.0. On Windows 2000 I am able to debug an
application via the remote debugger (gdbserver) on an ARM-LINUX target.
Using the same setup does not work reliable on Windows 7.
If I step through the application, at some point, the grey bar, which
marks the current
On 09/04/2014 12:06, Bernd Mueller wrote:
Hello,
I am using Lazarus 1.2.0. On Windows 2000 I am able to debug an
application via the remote debugger (gdbserver) on an ARM-LINUX target.
Using the same setup does not work reliable on Windows 7.
If I step through the application, at some point,
On 09/04/2014 17:27, Bernd Mueller wrote:
Martin Frb wrote:
Please run with a logfile:
http://wiki.lazarus.freepascal.org/GDB_Debugger_Tips#Log_info_for_debug_session
I have the log file attached.
What code is on this line?
Stepping will only work, if that code actually reaches the
26 matches
Mail list logo
