You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I hit a segfault issue trying to change up my build process a bit.
Long story short, I've narrowed the problem down to the first function call to anything linked from outside the main obj file. In this case, moving my function from the same file as main() to a different .o introduces a segfault on the call instruction and the calculated address looks wrong to me, but that's where my knowledge runs dry. it seems like the address of all the call instructions are off by a few bytes but I could be misreading or misinterpreting GDB output.
Relevant, my debugging symbols are borked per #14 and the stack trace is frankly dizzying without them.
If you give me a hint I can probably figure out the fix and PR it, I've been using this thing a bit and I want to better understand it, would enjoy contributing.
The text was updated successfully, but these errors were encountered:
I hit a segfault issue trying to change up my build process a bit.
Long story short, I've narrowed the problem down to the first function call to anything linked from outside the main obj file. In this case, moving my function from the same file as main() to a different .o introduces a segfault on the call instruction and the calculated address looks wrong to me, but that's where my knowledge runs dry. it seems like the address of all the call instructions are off by a few bytes but I could be misreading or misinterpreting GDB output.
Relevant, my debugging symbols are borked per #14 and the stack trace is frankly dizzying without them.
If you give me a hint I can probably figure out the fix and PR it, I've been using this thing a bit and I want to better understand it, would enjoy contributing.
The text was updated successfully, but these errors were encountered: