Skip to content
Advertisement

Tag: debugging

How do you determine where segfault occured when ip (null)?

segfault at 0 ip (null) sp bf9ed55c error 4 in appname[8048000+252000] If I don’t have the IP address, how do I determine where the crash occurred? does it being (null) mean anything useful? in the appname[8048000+262000] = 0x82Aa000 is that supposed to give a clue? is it the 0x82AA000 the value I should try to use, both nm output and

how to save “set solib-search-path”

I wonder linux gdb debugging. I have 1 execute file, 1 core dump file. so, I opened it in linux like this, but, I only show error message. so, I input command, and symbol read succeed. and, I input command and, I reopen dump file. like this, but still show same error message. I don’t want to show this error

Adjust context switch frequency in Java on Linux

I’m looking into a potential concurrency issue in some binary Java code. The code sometimes has a strange behavior, but I’m not sure if it’s actually due to concurrency issues in the code itself, or if it’s something else. I haven’t been able to reproduce the strange behavior myself, but only seen it happening in our log files. Is there

strace -e trace=network only showing SIGCHLD?

I am using the command: strace -tt -o ${filename} -e trace=network gdb –args ${EXECUTABLE} to track which system calls occur whilst connecting to and sending messages to a peer. However, I am only receiving the following entries: Should I not see the socket calls to read() close() etc? Answer Using strace with gdb –args ${EXECUTABLE} prints syscall of gdb, instead

gdb catch syscall condition and string comparisson

I would like to catch a system call (more specifically access) and set a condition on it based on string comparison (obviously for arguments that are strings). Specific example: when debugging ls I would like to catch access syscalls for specific pathnames (the 1st argument) int access(const char *pathname, int mode); So far, I have succeeded in manually inspecting the

How to catch new thread in gdb console mode?

I am running my Qt app from gdb, and i want to stop when new threads creates. (when gdb prints message [New Thread address (LPW number)]. I have set breakpoint b __pthread_create_2_1. That allows me to catch most of new threads prints. but i still got few new threads that are not catched. What else can i do to catch

Advertisement