Hi All
When I use my 32 bit binary on Solaris x86 machine, I get a segmentation
fault with the following stack trace.
libc.so.1`_malloc_unlocked+0x14c(4000, 3, 80a3130, 1, 8046a38, 805763f)
libc.so.1`malloc+0x39(4000, 0, 8046a1c, fef9e455, fef9158c, 4)
meta_del+0x13(2, 80a3100, 10, 0)
Alan Coopersmith wrote:
Girts Zeltins wrote:
Hello,
Where I can get feature list of SXDE 1/08?
It will be released when SXDE 1/08 is, which is still about
a month away, though it should mostly be the same set of
features found in Nevada build 79.
Is there available
Hi
I don't find a core dump generated when a SIGSEGV is received. I set the
LD_PRELOAD variable to watchmalloc.so.1 but could not find the actual
place of seg. fault as the core dump file is not generated. (I got the
stack trace I pasted when I attached mdb to the process) I don't have a
Sun
This is:
6367349 Panic on port_remove_event_doneq
which has been fixed in OpenSolaris about 1 1/2 years ago.
Since you're on Solaris 10, any rev released in 2007 has the patch for
this integrated.
For more details on S10 patch details or when/how fixed in S10, ask the
usual support channels
On what gnome is JDS based that will be shipped with SXDE 1/08?
I now use SXDE 9/07 and it's based on Gnome 2.18.x
It should be GNOME 2.20.x as in nevada 79.
Harry
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
On Mon, 24 Dec 2007, [EMAIL PROTECTED] wrote:
Hi
I don't find a core dump generated when a SIGSEGV is received. I set the
LD_PRELOAD variable to watchmalloc.so.1 but could not find the actual
place of seg. fault as the core dump file is not generated. (I got the
stack trace I pasted when I
When OSS can support 8-channel, 32 precision, and 192k sampling rate, as
well as other feathere,
what is the specific niftier features that it is lack of compared with ALSA?
A niftier acronym.
(PS: Sarcasm.)
-mg
signature.asc
Description: OpenPGP digital signature
Hi!
Yes, hello.
Then, Unix Admin asked mumbled
I don't mumble, and what I asked turned out to pertain to the paragraph I'm
going to quote from you, below. I know why I asked what I asked, and I turned
out to be correct:
something about
whether we might want to install Solaris on my
Brian Utterback wrote:
Joerg Schilling wrote:
The wish resulted in PSARC 2004/480 and I cannot understand why something
that
has been decided to be needed now has no people to work on. It seems that
there
is a problem in the way Sun is organized if this can happen.
An approved
Normally a *.d directory is for package-specific contributions to a
config file that are all handled together by the configured facility --
Linux has logrotate.d for all the log rotating specs from different
packages, and cron.d for specific cron additions, and so forth. Emacs
recognizes an
On Dec 24, 2007 6:44 PM, David Dyer-Bennet [EMAIL PROTECTED] wrote:
Normally a *.d directory is for package-specific contributions to a
config file that are all handled together by the configured facility --
Linux has logrotate.d for all the log rotating specs from different
packages, and
Gary:
Many Thanks for your help!.
I think there are 2 problems that I have here.
1. cde-login package hasn't been loaded on the operating system.
2. THe Network firewall has been blocking the X display from being sent on LAN.
I connected a network cable to the back of the server i.e. a
David Dyer-Bennet wrote:
(truth time: I'm going to be *so* happy when there's a decent ZFS
implementation in Linux and I can ditch this archaic pile of kludges.)
David,
I too am from a linux world, moving to Solaris because of zfs.
Sure - things are different, and some of the default
Ignacio Marambio Catán wrote:
On Dec 24, 2007 6:44 PM, David Dyer-Bennet [EMAIL PROTECTED] wrote:
Normally a *.d directory is for package-specific contributions to a
config file that are all handled together by the configured facility --
Linux has logrotate.d for all the log rotating specs
On Dec 24, 2007, at 4:44 PM, David Dyer-Bennet wrote:
Solaris has an /etc/cron.d directory, but the files in it aren't
crontab
files, and the man pages don't make any suggestion of anything except
user-specific cron files (no system cron file, either, that I can
find). So why the heck is
In the future, please send these to opensolaris-help, or
sysadmin-discuss. :) Also, check out:
http://www.genunix.org/wiki/index.php/OpenSolaris_New_User_FAQ
On Dec 25, 2007 12:23 AM, David Dyer-Bennet [EMAIL PROTECTED] wrote:
Ignacio Marambio Catán wrote:
On Dec 24, 2007 6:44 PM, David
On Dec 25, 2007, at 12:23 AM, David Dyer-Bennet wrote:
What happens to me every time I turn around on Solaris these days is
that tools I'm used to using are missing key features that I use every
day. Tar is missing the 'z' option, date is missing .
snip
And since Linux is what my work
On Dec 24, 2007 11:23 PM, David Dyer-Bennet [EMAIL PROTECTED] wrote:
Ignacio Marambio Catán wrote:
On Dec 24, 2007 6:44 PM, David Dyer-Bennet [EMAIL PROTECTED] wrote:
(truth time: I'm going to be *so* happy when there's a decent ZFS
implementation in Linux and I can ditch this archaic
Dale Ghent wrote:
On Dec 24, 2007, at 4:44 PM, David Dyer-Bennet wrote:
Solaris has an /etc/cron.d directory, but the files in it aren't crontab
files, and the man pages don't make any suggestion of anything except
user-specific cron files (no system cron file, either, that I can
find). So
I got branding error while trying to install informix on solaris environment.
Can anyone guide me how to fix this error..???
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
20 matches
Mail list logo
