|
|
Sponsored Content
Operating Systems
SCO
SCO 5.07 Panic / Core Dumps
Post 302091625 by ccarcher on Wednesday 4th of October 2006 04:36:49 AM
10-04-2006
|
|
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Does anyone know how to read core dumps. Is gdb the only tool for it ? The OS is Solaris.
Thanks (2 Replies)
Discussion started by: suntan
2 Replies
2. Solaris
I have the following set up on a Sun server running solaris 5.8 for core dump generation
coreadm
global core file pattern: /var/core
init core file pattern: /var/core
global core dumps: enabled
per-process core dumps: enabled
global setid core dumps:... (4 Replies)
Discussion started by: handak9
4 Replies
3. Programming
hi everyone,
Right now when I do:
strcmp(s1, s2);
i get a core dump because at times s1 or s2 can be nothing so that makes strcmp() core dump.
What is the solution, if at times I expect one of them (or both) to be NULL?
I want to be able to compare that s1 is NULL and s2 is "blah" or... (6 Replies)
Discussion started by: annie
6 Replies
4. UNIX for Advanced & Expert Users
Hi,
Can we modify the GDB source code so as to analyze core dumps from different targets? From my analysis, I think we need to build our section table statically for each target. i.e., including the various address boundaries in build_section_table() function. If this is the case, then the GDB... (2 Replies)
Discussion started by: nsdeeps
2 Replies
5. Programming
My program is not dumping core when hitting a segmentation violation inside a thread.
However, it dumps core when the segv occurs within main.
Any ideas on how to diagnose this?
AIX 5.3 (4 Replies)
Discussion started by: bean66
4 Replies
6. Solaris
i had a situation where a process was defunct. preap would not reap the process and gcore would not work properly (not sure why). therefore, the suggestion was to force a panic and collect the core dump. obviously you could do a savecore -L and capture the dump without bringing down the system.... (3 Replies)
Discussion started by: pupp
3 Replies
7. Ubuntu
Hello,
I am debugging a program which works as daemon. It sigfaults, unfortunately I'm unable to generate core dump file. Here is what I am doing:
tsurko@bastila:~$ ulimit -c unlimited
tsurko@bastila:~$ ulimit -c
unlimited
tsurko@bastila:~$ cat /etc/sysctl.conf | grep 'core_pattern'... (1 Reply)
Discussion started by: tsurko
1 Replies
8. Red Hat
Hi
I have a Fedora installed and I try to generate my application's core dump file.
My system has no coredump limit:
$ ulimit
core file size (blocks, -c) unlimited
But when my application crashes no core dumps generated. I can generate dump file using gcore but it is not appropraite... (1 Reply)
Discussion started by: xyzt
1 Replies
9. Programming
I'm working on a program in Linux with a group of people scattered around the country. When we have a crash, I like to send a core dump to the appropriate person so that they can understand the problem better. The problem is that our application uses several gigabytes worth of data and these... (4 Replies)
Discussion started by: bmsterner
4 Replies
10. HP-UX
kill -SEGV <pid> gives me the core file for that process but also terminates the process.
Can I not get the core dump without terminating the process ? (2 Replies)
Discussion started by: mohtashims
2 Replies
LEARN ABOUT NETBSD
ubt
UBT(4) BSD Kernel Interfaces Manual UBT(4) NAME
ubt -- USB Bluetooth driver SYNOPSIS
ubt* at uhub? port ? configuration ? interface ? DESCRIPTION
The ubt driver provides support for USB Bluetooth dongles to the Bluetooth protocol stack. USB Bluetooth dongles provide two interfaces, both of which the ubt driver claims. The second interface is used for Isochronous data and will have several alternate configurations regarding bandwidth consumption, which can be set using the hw.ubtN.config sysctl(8) variable. The number of alternate configurations is indicated by the value in the hw.ubtN.alt_config variable, and the isoc frame size for the current configuration is shown in the hw.ubtN.sco_rxsize and hw.ubtN.sco_txsize variables. By default, configuration 0 is selected, which means that no bandwidth is used on the Isochronous interface and no SCO data can be sent. Consult the Bluetooth USB specification at https://www.bluetooth.org/ for complete instructions on setting bandwidth consumption. The fol- lowing extract may be useful as a general guidance though details may differ between manufacturers. 0 No active voice channels 1 One voice channel with 8-bit encoding 2 Two voice channels with 8-bit encoding, or one voice channel with 16-bit encoding. 3 Three voice channels with 8-bit encoding 4 Two voice channels with 16-bit encoding 5 Three voice channels with 16-bit encoding SEE ALSO
bluetooth(4), uhub(4), sysctl(8) HISTORY
This ubt device driver was originally a character device written by David Sainty and Lennart Augustsson. It was rewritten to support socket based Bluetooth access for NetBSD 4.0 by Iain Hibbert. CAVEATS
Isochronous data is seemingly not well supported over USB in the current system and to get SCO working, you may have to calculate the SCO packet size that the stack will use. This is the sco_mtu value reported by the btconfig(8) command, and when combined with the SCO header (3 bytes) should fit exactly into an integer number of Isochronous data frames where the frame size is indicated by the 'hw.ubtN.sco_txsize' sysctl variable. For example: I want one voice channel (which is all that is supported, for now) so am using configuration #2, with a frame length of 17 bytes. This gives possible values of: (17 * 1) - 3 = 14 (17 * 2) - 3 = 31 (17 * 3) - 3 = 48 (17 * 4) - 3 = 65 (17 * 5) - 3 = 82 etc. btconfig(8) shows the maximum SCO payload as 64 bytes, so I am using the next smaller size of 48, to minimize the overhead of the 3 header bytes. The SCO packet size can be changed using the 'scomtu' option to btconfig(8). The failure mode is that the USB Bluetooth dongle locks up though generally removal/reinsertion will clear the problem. BUGS
The Isochronous configuration can only be changed when the device is not marked up. BSD
August 27, 2006 BSD