This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: gdb/1233: gdb causes 'abort' signal when debugging cvs
- From: <esp at pyroshells dot com>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 4 Jun 2003 02:28:00 -0000
- Subject: Re: gdb/1233: gdb causes 'abort' signal when debugging cvs
- Reply-to: <esp at pyroshells dot com>
The following reply was made to PR gdb/1233; it has been noted by GNATS.
From: <esp@pyroshells.com>
To: <gdb-gnats@sources.redhat.com>, <nobody@sources.redhat.com>
Cc:
Subject: Re: gdb/1233: gdb causes 'abort' signal when debugging cvs
Date: Tue, 3 Jun 2003 19:13:59 -0700 (PDT)
> Thank you very much for your problem report.
> It has the internal identification `gdb/1233'.
> The individual assigned to look at your
> report is: unassigned.
>
>>Category: gdb
>>Responsible: unassigned
>>Synopsis: gdb causes 'abort' signal when debugging cvs
>>Arrival-Date: Wed Jun 04 01:38:01 UTC 2003
I hope this is a real person I'm getting whilst responding to this, but I
figured out what was going on...
it looks like the signal is caused by following a fork into parent code,
whilst a child is running. 'set fork-follow-mode child' doesn't do squat,
nor 'set fork-follow-mode parent'. very irritating, I have to start
another version of gdb in another window.
Argh.
Ed