__kernel_vsyscall ()

Thread Tools Search this Thread
Top Forums Programming __kernel_vsyscall ()
# 1  
Old 07-09-2011
Error __kernel_vsyscall ()

I'm trying to compile a program called varkon, but after I chose an option from the main screen it gives me a segfault. The code is to long for me to go through it all, so I tried using gdb.
This was the output:
Reading symbols from /home/oliverj/Downloads/varkon/bin/xvarkon...(no debugging symbols found)...done.
[New Thread 25257]
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/ld-linux.so.2
Core was generated by `/home/oliverj/Downloads/varkon/bin/xvarkon'.
#0  0x0085e422 in __kernel_vsyscall ()

I don't see how this helps me find the error.
# 2  
Old 07-09-2011
It doesn't. If you compiled with debugging support (-ggdb) it'd probably give you a lot more.
# 3  
Old 07-10-2011
I tryed, but it still gave me the same message.
# 4  
Old 07-10-2011
What exactly did you try?
# 5  
Old 07-15-2011
I tried adding ggdb to the CFLAGS variable, but when I tryed to debug it, it was the same as the first time I tried it. Smilie
# 6  
Old 07-18-2011
Make sure the makefile's not stripping the output.
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. Red Hat

core dump analysis : __kernel_vsyscall ()

We have just enabled core dump on our RHEL5.7 OS. the java process is terminating very often so we enable core dump to analysis the issue and find below in core dump file. Core was generated by `/usr/java/jdk1.6.0_06//bin/java -server -Xms1536m -Xmx1536m -Xmn576m -XX:+Aggre'. Program... (0 Replies)
Discussion started by: pawankkamboj
0 Replies

2. Programming

C Sleep function hangs @ __kernel_vsyscall ()

This is the gdb backtrace. ^C Program received signal SIGINT, Interrupt. 0xffffe424 in __kernel_vsyscall () (gdb) bt #0 0xffffe424 in __kernel_vsyscall () #1 0xb7e56a70 in __nanosleep_nocancel () from /lib/libc.so.6 #2 0xb7e568bb in __sleep (seconds=0) at sleep.c:138 #3 0x080496d5 in... (6 Replies)
Discussion started by: dragonpoint
6 Replies
Login or Register to Ask a Question