08-08-2005
I think data adjacent to the pointer is overwriting the pointer in question - it's a so-called one-off error. One byte off - you are writing the LSB of a longword pointer.
The only way to fix this is to get into gdb, then examine the pointer after every line
of code is executed - just after you load the struct in get_dsp_data.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I'm a complete beginner at all this business so any help is appreciated.
I have a script (not written by me) which I need to modify. My problems is....
tail -1c $file
.... I understand this will return the final character of the $file variable. I need to make it return the first... (4 Replies)
Discussion started by: mastaCow
4 Replies
2. Programming
Hi, I try to marshal a unsigned int and a char * into a buffer, and then unmarshal them later to get them out. I need to put the char * in the front and unsigned int at the end of the buffer. However, my system always give me "BUS ERROR". I am using Sun Sparcs Sloris 2.10.
My code to marshal... (6 Replies)
Discussion started by: nj302
6 Replies
3. UNIX for Dummies Questions & Answers
Hello everbody:
when issuing the ulimit -a, on my tru64 machone, I get the following:
root@billing4# ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 10485760
stack(kbytes) 32768
memory(kbytes) 10190528
coredump(blocks) 0... (1 Reply)
Discussion started by: aladdin
1 Replies
4. Programming
helo can u tell me what do you mean by stack winding and stack unwinding
Regards,
Amit (2 Replies)
Discussion started by: amitpansuria
2 Replies
5. HP-UX
Hi,
I get a problem with stack overflow on HP-UX, when running a C program.
Pid 28737 received a SIGSEGV for stack growth failure.
Possible causes: insufficient memory or swap space,
or stack size exceeded maxssiz.
The possible cause i found, was that the definition of a structure had... (0 Replies)
Discussion started by: karthikb23
0 Replies
6. UNIX for Dummies Questions & Answers
I have a java process that piles up the stack memory.
ulimit -a
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 10
stack size ... (9 Replies)
Discussion started by: mohtashims
9 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I am new to the linux kernel development area. I want to know what is the difference between kernel mode stack and user mode stack? Does each process has a user mode stack and a kernel mode stack?? Or Each process has a user mode stack and there is only one kernel mode stack that is shared by... (4 Replies)
Discussion started by: saurabhkoar
4 Replies
8. Android
Running latest Android for Galaxy Tab 8.9 and bought a 32GB USB flash memory stick for file transfers, etc. Would not work. Searched the net for clues and could not find any. Then, back at the IT store, found out that Galaxy Tab currently only supports up to 16GB for the USD flash memory stick.... (0 Replies)
Discussion started by: Neo
0 Replies
LEARN ABOUT BSD
sigreturn
SIGRETURN(2) System Calls Manual SIGRETURN(2)
NAME
sigreturn - return from signal
SYNOPSIS
#include <signal.h>
struct sigcontext {
int sc_onstack;
long sc_mask;
int sc_sp;
int sc_fp;
int sc_ap;
int sc_pc;
int sc_ps;
};
sigreturn(scp);
struct sigcontext *scp;
DESCRIPTION
Sigreturn allows users to atomically unmask, switch stacks, and return from a signal context. The processes signal mask and stack status
are restored from the context. The system call does not return; the users stack pointer, frame pointer, argument pointer, and processor
status longword are restored from the context. Execution resumes at the specified pc. This system call is used by the trampoline code,
and longjmp(3) when returning from a signal to the previously executing program.
NOTES
This system call is not available in 4.2BSD, hence it should not be used if backward compatibility is needed.
The definition of the sigcontext structure is machine dependent (the structure cited above is that for a VAX running 4.3BSD); no program
should depend on its internal structure. Setjmp(3) may be used to build sigcontext structures in a machine independent manner.
RETURN VALUE
If successful, the system call does not return. Otherwise, a value of -1 is returned and errno is set to indicate the error.
ERRORS
Sigreturn will fail and the process context will remain unchanged if one of the following occurs.
[EFAULT] Scp points to memory that is not a valid part of the process address space.
[EINVAL] The process status longword is invalid or would improperly raise the privilege level of the process.
SEE ALSO
sigvec(2), setjmp(3)
NOTES (PDP-11)
On the PDP-11 the field sc_ap (argument pointer) does not exist and the field sc_fp (frame pointer) is the PDP-11 register r5. Addition-
ally, three new fields sc_r0, sc_r1 and sc_ovno are present on the PDP-11 which hold register values r0 and r1 and the text overlay number
to restore (see ld(1)).
struct sigcontext {
int sc_onstack; /* sigstack state to restore */
long sc_mask; /* signal mask to restore */
int sc_sp; /* sp to restore */
int sc_fp; /* fp to restore */
int sc_r1; /* r1 to restore */
int sc_r0; /* r0 to restore */
int sc_pc; /* pc to restore */
int sc_ps; /* psl to restore */
int sc_ovno /* overlay to restore */
};
4.3 Berkeley Distribution June 30, 1985 SIGRETURN(2)