* [ECOS] i386 gdb next problem
@ 2001-08-28 8:39 John Gumb
0 siblings, 0 replies; only message in thread
From: John Gumb @ 2001-08-28 8:39 UTC (permalink / raw)
To: 'ecos-discuss@sourceware.cygnus.com'
Jonathon,
Have you had chance to look at this / confirm whether this is an issue ?
If not, I'll continue plugging away & see if I can track it down.
Cheers,
John
> Hi,
> I also have such behaviour of the debugger.
> My host Linux Redhat 6.2.
> gdb version: i386-elf-gdb --verison returns GDB 5.0.
> eCos version (with Redboot) from anon CVS (Juli 25)
Okay, I don't know why that shouldn't work - certainly I was debugging on
the PC target from the anon cvs code just last week.
Perhaps it might behave better if the debugged app was built with no
optimization. Other than that, you'll need to investigate further (e.g. by
using "set debug remote 1" and seeing where GDB sets its "next" breakpoint
and see if that's valid).
------_=_NextPart_001_01C12FD7.54500910
Content-Type: text/html;
charset="ISO-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>i386 gdb next problem</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Jonathon,</FONT>
</P>
<P><FONT SIZE=2>Have you had chance to look at this / confirm whether this
is an issue ?</FONT>
</P>
<P><FONT SIZE=2>If not, I'll continue plugging away & see if I can track
it down.</FONT>
</P>
<P><FONT SIZE=2>Cheers,</FONT>
</P>
<P><FONT SIZE=2>John</FONT>
</P>
<P><FONT SIZE=2>> Hi,</FONT>
<BR><FONT SIZE=2>> I also have such behaviour of the debugger.</FONT>
<BR><FONT SIZE=2>> My host Linux Redhat 6.2.</FONT>
<BR><FONT SIZE=2>> gdb version: i386-elf-gdb --verison returns GDB
5.0.</FONT>
<BR><FONT SIZE=2>> eCos version (with Redboot) from anon CVS
(Juli 25)</FONT>
</P>
<P><FONT SIZE=2>Okay, I don't know why that shouldn't work - certainly I was
debugging on</FONT>
<BR><FONT SIZE=2>the PC target from the anon cvs code just last week.</FONT>
</P>
<P><FONT SIZE=2>Perhaps it might behave better if the debugged app was built
with no</FONT>
<BR><FONT SIZE=2>optimization. Other than that, you'll need to investigate
further (e.g. by</FONT>
<BR><FONT SIZE=2>using "set debug remote 1" and seeing where GDB
sets its "next" breakpoint</FONT>
<BR><FONT SIZE=2>and see if that's valid).</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C12FD7.54500910--
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2001-08-28 8:39 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-08-28 8:39 [ECOS] i386 gdb next problem John Gumb
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).