Missing a step in new(er) Remote gdb/kdb setup?
lonnie.vanzandt at ngc.com
Thu Aug 11 19:37:29 GMT 2005
I also noticed that my supfile for sources sets the tag to RELENG_5_4. I do
not know the FreeBSD CVS branching strategy well enough to know if perhaps
there is a RELENG_5 edit for kgdb already which I have missed because I have
limited the update to RELENG_5_4. Do you have ident information for a
known-to-be-working kgdb for FreeBSD 5.x?
On Thursday 11 August 2005 10:52 am, Lonnie VanZandt wrote:
> forgive me for grasping for straws, but, might I hope that those fixes are
> related to segfaults on initial connections? ;-) If so, what is the nature
> of the fix?
> On Thursday 11 August 2005 10:47 am, Marcel Moolenaar wrote:
> > On Aug 11, 2005, at 9:09 AM, Lonnie VanZandt wrote:
> > > Marcel,
> > >
> > > The protocol sync issue is now gone - but the host side kgdb
> > > core dumps
> > > immediately after reporting the current break point of the target:
> > *snip*
> > > Is there a kgdb patch/update for 5.4 release p3 that I should
> > > apply? Or
> > > perhaps some permission/resource issue on the host that needs to be
> > > corrected?
> > I committed a couple of fixes to -current, which I plan to merge to
> > RELENG_6
> > in a couple of days. I'll merge to RELENG_5 as well then.
> freebsd-current at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
More information about the freebsd-current