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: capture gdb output

[Andrew Cagney]

"Michael S. Miles" wrote:
> 
> Nicolas,
> 
> > > 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.
> >
> 
> > Isn't sufficient to use  "gdb ... 2>&1 | tee log.txt" ?
> 
> I just tried this and it works great!  My colleagues and I thank you so
> much!
> 
> I would still be interested in whether there is a function in gdb to open or
> close a log file during a session?

It is certainly listed in the TODO file:

--

Add a transcript mechanism to GDB.

Such a mechanism might log all gdb input and output to a file in a
form that would allow it to be replayed.  It could involve ``gdb
--transcript=FILE'' or it could involve ``(gdb) transcript file''.

--

	Andrew

RE: capture gdb output

[Michael S. Miles]

Nicolas,

> > 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.
>

> Isn't sufficient to use  "gdb ... 2>&1 | tee log.txt" ?

I just tried this and it works great!  My colleagues and I thank you so
much!

I would still be interested in whether there is a function in gdb to open or
close a log file during a session?

thanks,
michael miles

Re: capture gdb output

[Nicolas.Thery]

> 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.

Isn't sufficient to use  "gdb ... 2>&1 | tee log.txt" ?

(I don't have a unix machine handy and so can't test it).



**********************************************************************
Symbian Ltd is a company registered in England and Wales with registered number 01796587 and registered office at 19 Harcourt Street, London, W1H 4HF, UK.
This message is intended only for use by the named addressee and may contain privileged and/or confidential information. If you are not the named addressee you should not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify postmaster@symbian.com and delete the message and any attachments accompanying it immediately. Symbian does not accept liability for any corruption, interception, amendment, tampering or viruses occurring to this message in transit or for any message sent by its employees which is not in compliance with Symbian corporate policy.
**********************************************************************