Re: Unable to step through ARM code using insgiht-5.0

Re: Unable to step through ARM code using insgiht-5.0

[Ahmed A. Agbabiaka]

Hello,

Thank you all, for your suggestions regarding my GDB problem. I now have a
working version of GDB, "insight+dejagnu-20010205", which I have been using for
over one month now. However, I still have a few more queries:

My build of the snapshot (even though built using cygwin-1.1.18-2, on a WIN 95
platform) only works on Window NT. Attempts to use it on any WIN 95 machines
have failed miserably:
	- Downloading seems to hang half-way
	- When a download is successful, "step"ing crashes the debugger.

Are there any reasons why GDB should not work on a WIN 95 platform? Is this a
known problem, or just a one-off? I am yet to try it on a WIN 98 platform to see
if the same problems occur.

Thanks once again,
Ahmed

-----------------------------------------------------------------
This email is confidential and intended solely for the use of the
individual to whom it is addressed.
Any views or opinions presented are solely those of the author
and do not necessarily represent those of Thyron Limited.
If you are not the intended recipient then please be advised
that you have received this email in error and that any use,
dissemination, forwarding, printing or copying of this email 
is strictly prohibited.
If you have received this email in error, please notify the 
Thyron IT Administrator on +44 (0)1923 236 050 or 
send an email to mail-admin@thyron.com.
Thank You

capture gdb output

[Michael S. Miles]

I need to be able to capture all the output from my gdb session into some
type of log file.  It seems like this is a feature that would definitely
exist, but I have been searching the sources and documentation for any
mention of this capability with no luck.

Does anyone know if gdb has this functionality and if so, how to use it?

If it helps, I am using the 03/20/01 snapshot of GDB on a Linux-i386 system.
I am also using it as a remote Linux kernel debugger although I don't
believe that is relevant.

many thanks,
Michael Miles

Re: Unable to step through ARM code using insgiht-5.0

[Keith Seitz]

On Thu, 19 Apr 2001, Ahmed A. Agbabiaka wrote:

> Are there any reasons why GDB should not work on a WIN 95 platform? Is this a
> known problem, or just a one-off? I am yet to try it on a WIN 98 platform to see
> if the same problems occur.

FWIW, I've never had luck using gdb on Win95. However (the light at 
the end of the tunnel), I've also had NO problems using (and building, 
actually) on Win98, WinNT, or Win2000.

Keith

Re: capture gdb output

[Michael Meissner]

On Thu, Apr 19, 2001 at 08:54:04AM -0400, Michael S. Miles wrote:
> I need to be able to capture all the output from my gdb session into some
> type of log file.  It seems like this is a feature that would definitely
> exist, but I have been searching the sources and documentation for any
> mention of this capability with no luck.
> 
> Does anyone know if gdb has this functionality and if so, how to use it?
> 
> If it helps, I am using the 03/20/01 snapshot of GDB on a Linux-i386 system.
> I am also using it as a remote Linux kernel debugger although I don't
> believe that is relevant.

Besides using tee, you could run gdb within an emacs shell session (or use
emacs' gdb mode) and copy the buffer to a file, or use the 'script' command
that many Unixen provide (output is in the 'typescript' file).  On older
systems, xterm might have a logging option (which was disabled due to security
concerns).

-- 
Michael Meissner, Red Hat, Inc.  (GCC group)
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA
Work:	  meissner@redhat.com		phone: +1 978-486-9304
Non-work: meissner@spectacle-pond.org	fax:   +1 978-692-4482

Re: Unable to step through ARM code using insgiht-5.0

[Grant Edwards]

On Thu, Feb 15, 2001 at 04:01:14PM -0500, Fernando Nasser wrote:

> With the current versions of Cygwin it should work fine.
> 
> 
> But if you are using a b.20 or some other old version of Cygwin
> you may encounter problems with serial lines.  It gets worse
> the higher the speed you use. In this case, just grab the
> latest Cygwin and everything will be fine.

Or switch to Linux, and everything will be even finer.  ;)

-- 
Grant Edwards
grante@visi.com

Re: Unable to step through ARM code using insgiht-5.0

[Grant Edwards]

On Thu, Feb 15, 2001 at 11:30:10AM -0800, Keith Seitz wrote:

> [insight-related]
> > (Note: The "Continue to here" command" ignores ALL break points).
> 
> As discussed in the online help (select "Help->Help Topics..",
> then Source Window and Source Window Pop-up Menus), this is the
> intended behavior.
> 
> I'll leave to others more familiar with ARM support in gdb to
> address your other concerns. I will add, though, that I have
> never had any luck using ARM's rdi implementation (which they
> gave to gdb, no longer maintain, and are no longer interested
> in seeing kept up to date) at anything but 9600 baud.

I use RDI at 19200 (EmbeddedICE) and 38400 (Jeeni) with no
problems under Linux.  The serial/parallel combination also
works well under Linux, though Ethernet (Jeeni) is really the
way to go.

> What host/target are you using? I assume it's probably
> windows-hosted using rdi?

I've heard that serial RDI support under Widows/Cygwin has been
flakey in the past (and not worked at all under some versions
of Cygwin).

-- 
Grant Edwards
grante@visi.com

Re: Unable to step through ARM code using insgiht-5.0

[Fernando Nasser]

Keith Seitz wrote:
> 
> I'll leave to others more familiar with ARM support in gdb to address
> your other concerns. I will add, though, that I have never had any luck
> using ARM's rdi implementation (which they gave to gdb, no longer
> maintain, and are no longer interested in seeing kept up to date) at
> anything but 9600 baud.
> 

Yes, it works at 115200.  I have done it and other have as well.

The ARM AEB board (the $150 board they used to sell) has a bug in it and it would not follow the protocol so switching to a higher speed fails (thus it only works at 9600).
We tried to ask ARM about this and the answer was that we should buy the new $250 development board.


> What host/target are you using? I assume it's probably windows-hosted
> using rdi?
> 

With the current versions of Cygwin it should work fine.


But if you are using a b.20 or some other old version of Cygwin you may encounter problems with serial lines.  It gets worse the higher the speed you use.
In this case, just grab the latest Cygwin and everything will be fine.



-- 
Fernando Nasser
Red Hat - Toronto                       E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9

Re: Unable to step through ARM code using insgiht-5.0

[Keith Seitz]

On Thu, 15 Feb 2001, Ahmed A. Agbabiaka wrote:

[insight-related]
> (Note: The "Continue to here" command" ignores ALL break points).

As discussed in the online help (select "Help->Help Topics..", then 
Source Window and Source Window Pop-up Menus), this is the intended 
behavior.

I'll leave to others more familiar with ARM support in gdb to address 
your other concerns. I will add, though, that I have never had any luck 
using ARM's rdi implementation (which they gave to gdb, no longer 
maintain, and are no longer interested in seeing kept up to date) at 
anything but 9600 baud.

What host/target are you using? I assume it's probably windows-hosted 
using rdi?

Keith

Re: Unable to step through ARM code using insgiht-5.0

[Ahmed A. Agbabiaka]

Hello,

After my last correspondence, I obtained and built a GDB snapshot
(insight+dejagnu-20010205) for my ARM target - arm-riscix-coff. Although this
version gets me further than V5.0 ever did, I still have a few concerns...

Whenever I attempt to "step" through my code, DGB seems to hang. The only way
for me to run through my code is to use the "Continue to here" command that is
only selectable from a pop-up dialog whenever I "right-click", in the source
window,  on the line I would have had a break point on (Note: The "Continue to
here" command" ignores ALL break points).

GDB only seems to work (as described above) on my build machine. Copying the
installed GBD binaries onto other machines, GDB seems to be even more
unreliable. On some of my other machines I can connect at my desired baud rate
but when I attempt do download my application, GDB hangs. On a particular
machine I can only download at up to 19200. Any baud rate above that and...
...GDB hangs again.

Question, am I missing a very crucial step?

Any information to help me resolve these problems would be most appreciated.

Thanks,
Ahmed A. Agbabiaka


-----------------------------------------------------------------
This email is confidential and intended solely for the use of the
individual to whom it is addressed.
Any views or opinions presented are solely those of the author
and do not necessarily represent those of Thyron Limited.
If you are not the intended recipient then please be advised
that you have received this email in error and that any use,
dissemination, forwarding, printing or copying of this email 
is strictly prohibited.
If you have received this email in error, please notify the 
Thyron IT Administrator on +44 (0)1923 236 050 or 
send an email to mail-admin@thyron.com.
Thank You