This is the mail archive of the
insight@sources.redhat.com
mailing list for the Insight project.
Re: Insight hangs on segv trap
- To: guyr at zephion dot net
- Subject: Re: Insight hangs on segv trap
- From: Fernando Nasser <fnasser at redhat dot com>
- Date: Thu, 22 Feb 2001 11:48:50 -0500
- CC: fnasser at cygnus dot com, keiths at cygnus dot com, Insight List <insight at sources dot redhat dot com>
- Organization: Red Hat Canada
- References: <4F9E13BCC53ED411A629009027E8D00C02014A82@msg001.dcat.ops.broadbandoffice.net>
Glad to know that you are finally being able to use it.
I am even happier because you used one of the bug database major
features: provide solutions to know problems :-)
Thanks for your interest on Insight and I hope you enjoy using it.
Regards,
Fernando
> guyr@zephion.net wrote:
>
> Fernando and Keith, I got this working. I went to the Insight bug
> database and saw PR 49. Symptoms sounded like what I was
> experiencing, so following the advice in that PR, I downloaded the
> latest weekly build and recompiled. Everything now works.
>
> I'd suggested replacing the current advertised download with the
> latest weekly. Thanks for your assistance.
>
> -----Original Message-----
> From: Fernando Nasser [mailto:fnasser@cygnus.com]
> Sent: Wednesday, February 21, 2001 1:20 PM
> To: guyr@zephion.net
> Cc: insight@sourceware.cygnus.com
> Subject: Re: Insight hangs on segv trap
>
> > guyr@zephion.net wrote:
> >
> > I used the dummy test program below to test the various debuggers
> I'm trying. When I went through this program in Insight using the Next
> button (step over), when I Next'd over the strcpy() line, the source
> in the window disappeared and the mouse pointer turned into a clock
> and stayed that way. The only way I could get out was to close the
> debugger window and restart it. Should I submit this as a bug report?
>
> >
> > #include <iostream.h>
> > #include <string.h>
> >
> > void main()
> > {
> > char* p = NULL;
> >
> > cout << "Hello, world" << endl;
> >
> > strcpy(p, "crash me");
> > cout << "Crash time: " << p << endl;
> > }
>
> Please try the command line "next" (without the GUI) first to see if
> it works.
>
> Now that you have a GUI-enabled GDB, use "gdb -nw" to start it in
> command line mode.
>
> If next is not working in command line mode it is a GDB bug, so it
> must be reported to the GDB bug database.
>
> If it is a GUI only problem, by all means, please add it to the
> Insight bug database. Don't forget to specify the version, which
> host, which target etc. The above works fine in my machine for
> instance, so it may be specific to a certain type of system.
>
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9