and line, and also it frequently freezes
to the point where you have to kill the window. gdb-4.17 is much better
for C++.
Richard Cownie ([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
most useful version
I've seen for debugging C++).
Richard Cownie ([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
oblems compiling gdb/solib.c
Richard Cownie ([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
.
So to do any real work you need gdb-4.17, which is a great advance on its successor.
However, the port of gdb-4.17 has disappeared, and the old port in my version
4.0-19990604-CURRENT does not build.
Does anyone have patches to get gdb-4.17 working in 4.0-CURRENT ?
Thanks
Richard Cownie
u try a kernel built from sources with the
> POST_SMP_VMSHARE tag? I may have broken something during the commit.
Have to get out the door right now, will try this either tomorrow morning
or Monday.
Thanks
Richard Cownie
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubs
It would also be good if this probing
I've tried various hacks to this code, but have not succeeded in making it
work for 4GB. Changing "int end" to "vm_offset_t end" is not sufficient.
It has a tendency to say "Too many holes in address space" ... Even
defining MAXMEM does not solve the problem.
Richard Cownie (t...@ma.ikos.com)
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
any tweaking,
which would simplify installation - I get nervous shuffling DIMMs
in and out of the machine ...
Thanks
Richard Cownie (t...@ma.ikos.com)
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
