For background on what this is, see:
http://www.opensolaris.org/jive/message.jspa?messageID=24416#24416
http://www.opensolaris.org/jive/message.jspa?messageID=25200#25200
=
opensolaris-code-discuss 04/16 - 04/30
=
Size of all threa
snow wrote:
Thanks to all.
What are mdb debugger components?Can Oliver Yang
give me an example?
It allows you do some extension for mdb by writing a new mdb debugger
module. You could developer your own debugger module for mdb.
For example, mdb on Solaris 10 support a dcmd ::memstat, but
Thanks to all.
What are mdb debugger components?Can Oliver Yang
give me an example?
This message posted from opensolaris.org
___
opensolaris-code mailing list
opensolaris-code@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opensolaris-c
Manu Curious wrote:
Hi everyone,
I'm using mmap to map a large file in to my proc's as. Thereafter i
want to munmap a small chunk in "middle" of it.
I tried munmap but got "Invalid arguments" error.
munmap manpage says that the addr passed to munmap should be same as
used in earlier mmap ca
Hi everyone,
I'm using mmap to map a large file in to my proc's as. Thereafter i want to
munmap a small chunk in "middle" of it.
I tried munmap but got "Invalid arguments" error.
munmap manpage says that the addr passed to munmap should be same as used in
earlier mmap call or else unpredictable
> sigh.. this is a painful place to be. I've had to
> debug my way out of here several times. Kernel boot
> fails at mount root due to any number of previous
> errors.
> The message when it fails is not helpful. There's
> also
> not a silver bullet to finding the problem.
I see it as an opportunity
On 29/05/07, Garrett D'Amore <[EMAIL PROTECTED]> wrote:
No, and I mis-stated the above restriction. The restriction should
apply to mutexes held _across_ cv_wait. The mutex passed as an argument
to cv_wait is dropped by cv_wait, and not held during the sleep call, so
it can be acquired to do c
On 30/05/07, snow <[EMAIL PROTECTED]> wrote:
I have written a module.I can load it by modload,but when I debug it
under mdb -k as follow:
>::load /gdx/Testmod
(but i got error message)
mdb:ld.so.1:mdb:fatal:relocation error:file /gdx/Testmod:symbol
mod_install:referencef symbol not found
Have
snow wrote:
I have written a module.I can load it by modload,but when I debug it
under mdb -k as follow:
::load /gdx/Testmod
(but i got error message)
mdb:ld.so.1:mdb:fatal:relocation error:file /gdx/Testmod:symbol
mod_install:referencef symbol not found
::load dcmd is used for lo
I have written a module.I can load it by modload,but when I debug it
under mdb -k as follow:
>::load /gdx/Testmod
(but i got error message)
mdb:ld.so.1:mdb:fatal:relocation error:file /gdx/Testmod:symbol
mod_install:referencef symbol not found
This message posted from opensolaris.org
___
>Does anyone know when the new POSIX-draft versions of |mkdirat()|&co.
>(e.g |mkdirat()|, |faccessat()|, |fchmodat()|, |fchownat()|,
>|fstatat()|, |linkat()|, |mknodat()|, |openat()|, |symlinkat()|,
>|unlinkat()|, |utimensat()|) will be available in Solaris (AFAIK these
>functions were added to th
snow stated:
< The content I got from command line with modinfo is different from the
content I got from MDB -K with ::dmods,is it right?
Well yes. dmods are the Debugger Modules (extenstions to mdb if you will).
Whereas modinfo tells you the Solaris OS modules (aka drivers) that are
curr
12 matches
Mail list logo