Thread: Unable to get debugging info to track down a segfault

I've uploaded my code to
GitHub - awsdert/gasp at 53a48dbfab059b5b3bfb285ac18e3d1002de106e

Someone mind taking a look to see if they can discern why I'm not getting debug info, if you're gonna run it yourself then type "make gede" into the terminal in root of the cloned project, that will first launch "gede gasp-d" which will then launch "pkexec gede deep-gasp-d" (refer to output for full details of the launch)

As for the segfault I can hazard a guess to it being in proc_handle_bytescanner() but I'm not certain as it could also be the interaction with lua at the point it's supposed to hand over, the reason I think it is in bytescanner() is because I do boundary scans there, proc_handle_dump() doesn't care about boundaries cause it's just dumping to file.

Originally Posted by Salem

Code:

%.o: %
	$(CC) $(CFLAGS) -o $@ -c $< $(LIBS)

%-d.o: %
	$(CC) $(DFLAGS) $(CFLAGS) -o $@ -c $< $(LIBS)

Maybe because your .o rule lacks DFLAGS.

That's supposed to lack that, the "-d" is for distinguishing debug files from normal files

Originally Posted by stahta01

Does the order in the makefile result "%.o: %" being used instead of "%-d.o: %"?
I have no idea if order makes a different in makefiles.

Tim S.

Only when I use normal targets, turned out there was a segfault in proc_handle_dump() though, forgot to convert a piece of code to no longer add to the base pointer, still seem to be getting a segfault elsewhere though (trying to catch it atm)

Originally Posted by awsdert

Only when I use normal targets, turned out there was a segfault in proc_handle_dump() though, forgot to convert a piece of code to no longer add to the base pointer, still seem to be getting a segfault elsewhere though (trying to catch it atm)

Found it, turned out I had accidentally 0'd the swap pointers for mapped regions, now I just gotta find where I'm getting an infinite loop