Mdb : missing modules on Solaris 10 ??

Question

I'm trying to debug a core using mdb.
All of the web pages I look at show commands like "::ps" and "::pgrep".
These would be great, but I don't see any of these when I enter "::dcmds" nor "::dmods -l".
It looks like the "modules" are in /usr/lib/mdb/proc.
Does anyone know where these modules are or how I can get them for Solaris 10?
unix
genunix
ip
nfs
ipc
krtld
pecfs
cpu.generic
uppc
scsi_vhci
ufs
hook
neti
sctp
arp
usba
nca
lofs
zfs
random
nsctl
sdbc
rdc
sppp
When I start mdb using a core file it only shows 3 *.so.* "modules" being loaded:
-bash-3.00$ mdb 5549.core
Loading modules: [ libc.so.1 libuutil.so.1 ld.so.1 ]
Also, in the examples I've seen online are using an "object" file and a "core" file:
# mdb unix.0 vmcore.0
Loading modules: [ unix genunix specfs cpu.generic uppc scsi_vhci ufs ip hook neti sctp arp usba nca lofs zfs random nsctl sdbc rdc sppp ]
>
(e.g http://www.c0t0d0s0.org/archives/4389-Less-known-Solaris-features-About-crashes-and-cores-Part-4-Crashdump-analysis-for-beginners.html)

Answer 1

pkwooster wrote:
Joe, I know that you are a skeptic, and need proof for everything said. I heard about the demise of Access, or more correctly the database most frequently associated with the Access front end, JET, several years ago from a Microsoft employee. Yet it is still here.
There is plenty of documentation online about this. Here's just one example: http://www.answers.com/topic/microsoft-jet-database-engine?cat=technology. MS themselves are rather less clear.
That link would suggest that MS Access 2007 is not in fact SQL Server.
MS has been trying for at least 5 years to wean its users off Access-JET and onto one flavour or another of SQL/Server. I'm a Microsoft Partner and see their marketing on a regular basis. Access is rarely mentioned and SQL Server is a hot topic. Note that most MS/Office applications, such as Outlook now use SQL/Server.Ok.
However marketing is different than technology. In terms of that I can only note that I don't see Bob on my desktop.
And Office 2007 is still using Access (which apparently is not SQL Server according to what you posted.)
Conversely, for example, Microsoft has specifically announced that FoxPro will no longer be supported.
Thus I am still looking for something that would suggest that either it is SQL Server right now (2007) or that it shortly will be - like perhaps the beta for the next version is.
And I can only note that some of the stuff that Access does would be difficult to seamlessly do via SQL Server. The article that you posted suggests that upgrades from MS Access exist but that those can lose functionality that will require manual work to replace. Thus if MS did decide to replace Access in Office with SQL Server they would need to come up with a solution for that or risk people not upgrading.
I am not claiming that this can't happen but rather that I question whether it is relevant to suggest that it anything of concern in the near future (especially for an app that is targeting it anyways.)