Search:

Type: Posts; User: kruemelmonster

Search: Search took 0.00 seconds.

  1. Replies
    12
    Views
    8,125

    That's good enough to be able to debug. Thanks a...

    That's good enough to be able to debug.
    Thanks a lot for your help!
  2. Replies
    12
    Views
    8,125

    Oh wow, thanks! Don't know how I could have...

    Oh wow, thanks!
    Don't know how I could have missed that!

    Do you have any idea how to catch the signal using gdb?
    The handler gets installed successfully (checked with my updated if-statement...
  3. Replies
    12
    Views
    8,125

    In the meantime I figured out, that the signal...

    In the meantime I figured out, that the signal handler does not catch the signal if I run the program in gdb, but does catch it if I run it normally.

    However


    if(0 > sigaction(SIGSEGV,...
  4. Replies
    12
    Views
    8,125

    Thank you very much for your replies! I solved...

    Thank you very much for your replies!
    I solved it by requiring a write lock to be held in order to write, and assume that the access is a read if the lock is not held.

    However another problem...
  5. Replies
    12
    Views
    8,125

    I encountered another problem. Is it possible to...

    I encountered another problem.
    Is it possible to determine whether the fault occured because of an attempt to read or to write?
    I'd assume, that this can be done using siginfo_t, but can't figure...
  6. Replies
    12
    Views
    8,125

    Makes sense, thank you very much!

    Makes sense, thank you very much!
  7. Replies
    12
    Views
    8,125

    Get faulting address on SIGSEGV

    Hey all,

    I try to write a shared memory for a distributed computing system.

    In order to implement a kind of paging for this I want to invalidate the addresses of memory-pages that are currently...
Results 1 to 7 of 7