git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Segfault on merge with 1.6.2.1

From
Miklos Vajna <vmiklos@frugalware.org>
Date
Mar 30, 2009, 11:03 UTC
Message-ID
<20090330110335.GF22446@genesis.frugalware.org>
In-Reply-To
<op.urk20nanso3nzr@sulidor.mdjohnson.us>
On Sun, Mar 29, 2009 at 09:39:49PM -0500, Michael Johnson <redbeard@mdjohnson.us> wrote:
Show 6 quoted lines
> Well, I've got a backtrace, but I don't have debugging symbols,  
> apparently. There is not a Debian package I can find that has them. I  
> checked debug.debian.net, as well as the standard sid repository. So I  
> will have to rebuild the package with debugging turned on. I will not be  
> able to do that tonight, unfortunately. I will probably have a chance  
> tomorrow evening.

Okay, no rush. In case Dscho's patch does not fix your problem, please rebuild git with debug symbols enabled and send a normal trace.

Thanks.
Previous: Johannes SchindelinNext: Michael Johnson
Message 5 of 18 in “Segfault on merge with 1.6.2.1”
  1. Michael JohnsonMar 28, 2009
  2. Miklos VajnaMar 29, 2009
  3. Michael JohnsonMar 30, 2009
  4. Johannes SchindelinMar 30, 2009
  5. Miklos VajnaMar 30, 2009
  6. Michael JohnsonMar 31, 2009
  7. Michael JohnsonApr 1, 2009
  8. Miklos VajnaApr 1, 2009
  9. Clemens BuchacherApr 1, 2009
  10. Michael JohnsonApr 2, 2009
  11. Clemens BuchacherApr 5, 2009
  12. 1/3 add tests for merging with submodulesClemens Buchacher, Apr 5, 2009
  13. 2/3 update cache for conflicting submodule entriesClemens Buchacher, Apr 5, 2009
  14. 3/3 simplify output of conflicting mergeClemens Buchacher, Apr 5, 2009
  15. Junio C HamanoApr 5, 2009
  16. Johannes SchindelinApr 5, 2009
  17. Michael JohnsonApr 6, 2009
  18. Clemens BuchacherApr 6, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.